<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Caching on Lorbic</title>
    <link>https://lorbic.com/tags/caching/</link>
    <description>Recent content in Caching on Lorbic</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Wed, 22 Jul 2026 12:00:00 +0530</lastBuildDate>
    <atom:link href="https://lorbic.com/tags/caching/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Cache-Driven Development: Saving Your Database From Itself</title>
      <link>https://lorbic.com/cache-driven-development/</link>
      <pubDate>Wed, 22 Jul 2026 12:00:00 +0530</pubDate>
      <guid>https://lorbic.com/cache-driven-development/</guid>
      <description>&lt;p&gt;There is a moment in every backend engineer&amp;rsquo;s life when their database starts refusing connections.&lt;/p&gt;&#xA;&lt;p&gt;Picture 2 a.m. on a Tuesday. The app is operating under normal traffic, nothing unusual. But the database connection pool is saturated. Queries are timing out. The monitoring dashboard shows 50,000 database operations per second, far beyond what the system should be handling.&lt;/p&gt;&#xA;&lt;p&gt;When someone pulls the slow-query logs, the pattern is immediately clear. The same query appears thousands of times:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
