<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Databases on Fullstack with Santosh</title><link>https://santoshk.dev/tags/databases/</link><description>Recent content in Databases on Fullstack with Santosh</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Santosh Kumar</copyright><lastBuildDate>Tue, 04 Aug 2026 00:09:14 +0530</lastBuildDate><atom:link href="https://santoshk.dev/tags/databases/index.xml" rel="self" type="application/rss+xml"/><item><title>Database Normalization: Scratching the Database Surface</title><link>https://santoshk.dev/posts/2022/database-normalization-scratching-the-database-surface/</link><pubDate>Sat, 05 Nov 2022 11:16:13 +0000</pubDate><guid>https://santoshk.dev/posts/2022/database-normalization-scratching-the-database-surface/</guid><description>&lt;h2 class="relative group"&gt;Introduction
 &lt;div id="introduction" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#introduction" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;Database normalization is the process of structuring a database, in accordance with a series of normal forms in order to reduce data redundancy and improve integrity.&lt;/p&gt;
&lt;p&gt;In other words, &lt;strong&gt;database normalization&lt;/strong&gt; is basically breaking a table into two to prevent repetitive columns aka data redundancy. It entails organizing the columns (attributes) and tables (relations) of a database to ensure that their dependencies are properly enforced by database integrity constraints. It is accomplished by applying some formal rules either by a process of synthesis (creating a new database design) or decomposition (improving an existing database design).&lt;/p&gt;</description></item><item><title>Sending POST Request in Go with a Body</title><link>https://santoshk.dev/posts/2020/sending-post-request-in-go-with-a-body/</link><pubDate>Sat, 20 Jun 2020 17:30:15 +0530</pubDate><guid>https://santoshk.dev/posts/2020/sending-post-request-in-go-with-a-body/</guid><description>&lt;h3 class="relative group"&gt;Introduction
 &lt;div id="introduction" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#introduction" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h3&gt;
&lt;p&gt;Send a POST request in golang is pretty daunting if you have a post body and you&amp;rsquo;re coming from a scripting language like JavaScript or Python. Here in Go, schema for JSON needs to be defined beforehand in order to marshal and unmarshal string back and forth to JSON.&lt;/p&gt;

&lt;h2 class="relative group"&gt;Simple POST
 &lt;div id="simple-post" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#simple-post" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;This marshaling/unmarshalling could be an oneliner if your request body is not nested, or is one level deep, or there is not even a body. Consider this example:&lt;/p&gt;</description></item><item><title>Introduction to BoltDB</title><link>https://santoshk.dev/posts/2020/introduction-to-boltdb/</link><pubDate>Sun, 10 May 2020 02:02:46 +0530</pubDate><guid>https://santoshk.dev/posts/2020/introduction-to-boltdb/</guid><description>&lt;h2 class="relative group"&gt;Why use BoltDB
 &lt;div id="why-use-boltdb" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#why-use-boltdb" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h2&gt;
&lt;p&gt;Bolt plays pretty well with Go&amp;rsquo;s concurrency model, we can do multiple reads concurrently.&lt;/p&gt;
&lt;p&gt;For pro and cons, I will contrast it with similar database SQLite. I have done SQLite when I worked with Xentrix to develop GUI tools for the artists.&lt;/p&gt;
&lt;p&gt;You may want to &lt;a href="https://www.linkedin.com/in/sntshk/" target="_blank" rel="noreferrer"&gt;connect with me on LinkedIn&lt;/a&gt;.&lt;/p&gt;

&lt;h3 class="relative group"&gt;Pro
 &lt;div id="pro" class="anchor"&gt;&lt;/div&gt;
 
 &lt;span
 class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"&gt;
 &lt;a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#pro" aria-label="Anchor"&gt;#&lt;/a&gt;
 &lt;/span&gt;
 
&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;It is native go.&lt;/strong&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;This means you don&amp;rsquo;t need any database server running, like SQLite. In oppose to &lt;em&gt;Redis&lt;/em&gt; and &lt;em&gt;memcached&lt;/em&gt;.&lt;/p&gt;</description></item></channel></rss>