<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Writes on The Coders Blog</title><link>https://thecodersblog.com/tag/writes/</link><description>Recent content in Writes on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 11 May 2026 03:54:52 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/writes/index.xml" rel="self" type="application/rss+xml"/><item><title>Lakebase Architecture: Accelerating Postgres Writes</title><link>https://thecodersblog.com/lakebase-architecture-for-faster-postgres-writes-2026/</link><pubDate>Mon, 11 May 2026 03:54:52 +0000</pubDate><guid>https://thecodersblog.com/lakebase-architecture-for-faster-postgres-writes-2026/</guid><description>&lt;p&gt;For years, PostgreSQL has been the darling of database administrators and data engineers worldwide, revered for its robustness, extensibility, and adherence to SQL standards. Yet, like any battle-tested technology, it has its Achilles&amp;rsquo; heel. For write-heavy Online Transaction Processing (OLTP) workloads, a fundamental mechanism designed for durability has inadvertently become a significant performance bottleneck: &lt;strong&gt;Full Page Writes (FPW)&lt;/strong&gt;. Today, we&amp;rsquo;re diving deep into the Lakebase architecture, a groundbreaking shift promising to shatter these limitations and unlock unprecedented write performance for PostgreSQL.&lt;/p&gt;</description></item></channel></rss>