<?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 The Coders Blog</title><link>https://thecodersblog.com/categories/databases/</link><description>Recent content in Databases on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 06 May 2026 22:26:38 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/categories/databases/index.xml" rel="self" type="application/rss+xml"/><item><title>Microsoft Dev: Azure Cosmos DB Conf 2026 Recap: Lessons from Production</title><link>https://thecodersblog.com/azure-cosmos-db-production-lessons-2026-2026/</link><pubDate>Wed, 06 May 2026 22:26:38 +0000</pubDate><guid>https://thecodersblog.com/azure-cosmos-db-production-lessons-2026-2026/</guid><description>&lt;p&gt;You provisioned Azure Cosmos DB with ample Request Units (RUs), your application&amp;rsquo;s P99 latency is creeping up, and throttling errors are becoming more frequent. Sound familiar? This isn&amp;rsquo;t a capacity problem; it&amp;rsquo;s a design problem. The Azure Cosmos DB Conference 2026 made one thing brutally clear: the platform exposes your data modeling and partition key choices like a harsh spotlight.&lt;/p&gt;
&lt;h2 id="the-unseen-bottleneck-partition-keys-and-skewed-distribution"&gt;The Unseen Bottleneck: Partition Keys and Skewed Distribution&lt;/h2&gt;
&lt;p&gt;The single most impactful decision you make for Cosmos DB is the partition key. Forget throwing more RUs at the problem; if your partition key leads to skewed distribution, you&amp;rsquo;re battling hot partitions. This results in 100% RU utilization on some physical partitions while others languish, leading to relentless throttling and unacceptable latency spikes, even if your aggregate RU usage appears low.&lt;/p&gt;</description></item><item><title>PHP-fts: Building a Full-Text Search Engine in Pure PHP</title><link>https://thecodersblog.com/php-full-text-search-engine-2026/</link><pubDate>Wed, 06 May 2026 22:01:09 +0000</pubDate><guid>https://thecodersblog.com/php-full-text-search-engine-2026/</guid><description>&lt;p&gt;Ever found yourself wrestling with database &lt;code&gt;LIKE&lt;/code&gt; queries, desperately trying to simulate fuzzy matching or relevance scoring, only to end up with sluggish performance and brittle code? The dream of a truly powerful search integrated seamlessly into your PHP application without external infrastructure often feels just that: a dream. Until now.&lt;/p&gt;
&lt;h3 id="the-core-problem-native-search-vs-external-dependencies"&gt;The Core Problem: Native Search vs. External Dependencies&lt;/h3&gt;
&lt;p&gt;For many PHP developers, adding robust full-text search capabilities to a project presents a dilemma. On one hand, you have the well-established, high-performance solutions like Elasticsearch and Solr. These are formidable search engines, offering scalability, advanced relevance tuning, and a wealth of features. However, they demand dedicated infrastructure, complex setup, and ongoing maintenance—a significant overhead for many projects.&lt;/p&gt;</description></item><item><title>Beyond Filesystems: Why Your Private GitHub Should Run on Postgres [2026]</title><link>https://thecodersblog.com/my-private-github-on-postgres-2026/</link><pubDate>Fri, 01 May 2026 21:09:51 +0000</pubDate><guid>https://thecodersblog.com/my-private-github-on-postgres-2026/</guid><description>&lt;p&gt;For too long, the bedrock of our version control—Git itself—has been inextricably linked to the filesystem. But what if we told you that for your private GitHub instance, this isn&amp;rsquo;t just an outdated constraint, but a fundamental barrier to the control and insight your sophisticated workflows demand?&lt;/p&gt;
&lt;h2 id="the-filesystems-shackles-why-git-needs-a-new-home"&gt;The Filesystem&amp;rsquo;s Shackles: Why Git Needs a New Home&lt;/h2&gt;
&lt;p&gt;Git, in its conventional design, treats content-addressable data as files on disk. These files reference each other via &lt;strong&gt;SHA-1 hashes&lt;/strong&gt;, forming a directed acyclic graph that represents your project&amp;rsquo;s history. This model has served us incredibly well for decades, providing robust, distributed version control.&lt;/p&gt;</description></item><item><title>Postgres: The Unsung Scaling Hero? Benchmarking Workflow Execution in 2026</title><link>https://thecodersblog.com/does-postgres-scale-2026/</link><pubDate>Fri, 01 May 2026 07:55:24 +0000</pubDate><guid>https://thecodersblog.com/does-postgres-scale-2026/</guid><description>&lt;p&gt;You&amp;rsquo;re building complex workflow execution systems, pushing millions of tasks daily, and your first thought for a database probably wasn&amp;rsquo;t Postgres. Let&amp;rsquo;s talk about why it &lt;strong&gt;should&lt;/strong&gt; have been, and how to prove it.&lt;/p&gt;
&lt;h2 id="the-elephant-in-the-room-dispelling-the-postgres-doesnt-scale-myth"&gt;The Elephant in the Room: Dispelling the &amp;lsquo;Postgres Doesn&amp;rsquo;t Scale&amp;rsquo; Myth&lt;/h2&gt;
&lt;p&gt;The developer community often falls prey to an oversimplified, binary narrative: a database either scales or it doesn&amp;rsquo;t. This rigid thinking stifles nuanced architectural discussions and leads to premature dismissal of robust technologies. It&amp;rsquo;s a dangerous trap for senior engineers aiming to build durable, high-performance systems.&lt;/p&gt;</description></item><item><title>Linux 7.0: How a Kernel Preemption Bug Crippled PostgreSQL Performance in 2026</title><link>https://thecodersblog.com/linux-kernel-7-0-preemption-regression-impact-on-postgresql-2026/</link><pubDate>Wed, 29 Apr 2026 16:57:18 +0000</pubDate><guid>https://thecodersblog.com/linux-kernel-7-0-preemption-regression-impact-on-postgresql-2026/</guid><description>&lt;p&gt;In April 2026, the Linux Kernel 7.0 release promised evolutionary advancements, but for PostgreSQL users, it delivered a brutal, silent performance regression, abruptly halving throughput on critical production workloads without a single error message.&lt;/p&gt;
&lt;h2 id="the-silent-killer-how-linux-70-blindfolded-postgresql"&gt;The Silent Killer: How Linux 7.0 Blindfolded PostgreSQL&lt;/h2&gt;
&lt;p&gt;The eagerly awaited release of Linux Kernel 7.0 in early 2026 was met with the usual anticipation within the open-source community. Touted for its efficiency improvements and new hardware support, it was expected to be a solid, if not revolutionary, upgrade. Yet, for database administrators and cloud engineers managing high-performance PostgreSQL instances, it brought an unforeseen and devastating impact.&lt;/p&gt;</description></item><item><title>Rocky: Rust SQL Engine with Data Versioning 2026</title><link>https://thecodersblog.com/rocky-a-rust-sql-engine-with-advanced-data-versioning-2026/</link><pubDate>Wed, 29 Apr 2026 10:02:14 +0000</pubDate><guid>https://thecodersblog.com/rocky-a-rust-sql-engine-with-advanced-data-versioning-2026/</guid><description>&lt;p&gt;The landscape of data management is perpetually evolving, demanding more robust, auditable, and flexible systems. Today, we introduce Rocky, a novel SQL engine engineered in Rust, fundamentally reshaping how developers interact with data through advanced versioning capabilities. Rocky integrates Git-like data branching, comprehensive replay functionality, and granular column lineage, addressing critical challenges in data integrity, collaboration, and debugging for modern data-intensive applications.&lt;/p&gt;
&lt;h3 id="data-branching-git-native-version-control-for-your-database"&gt;Data Branching: Git-Native Version Control for Your Database&lt;/h3&gt;
&lt;p&gt;Rocky&amp;rsquo;s core innovation lies in its native support for data branching. This mechanism mirrors the workflow familiar to every software developer using Git, allowing for the creation of isolated, mutable copies of a database&amp;rsquo;s state. Instead of managing schema changes or data transformations through cumbersome migrations or staging environments, developers can now &lt;code&gt;BRANCH&lt;/code&gt; their entire database.&lt;/p&gt;</description></item></channel></rss>