<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Scalability on Lorbic</title><link>http://localhost:1313/tags/scalability/</link><description>Recent content in Scalability on Lorbic</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 22 Jul 2026 12:00:00 +0530</lastBuildDate><atom:link href="http://localhost:1313/tags/scalability/index.xml" rel="self" type="application/rss+xml"/><item><title>Cache-Driven Development: Saving Your Database From Itself</title><link>http://localhost:1313/cache-driven-development/</link><pubDate>Wed, 22 Jul 2026 12:00:00 +0530</pubDate><guid>http://localhost:1313/cache-driven-development/</guid><description>&lt;p>There is a moment in every backend engineer&amp;rsquo;s life when their database starts refusing connections.&lt;/p>
&lt;p>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>
&lt;p>When someone pulls the slow-query logs, the pattern is immediately clear. The same query appears thousands of times:&lt;/p></description></item><item><title>What Facebook's Memcache Taught Me About Systems Thinking</title><link>http://localhost:1313/scaling-memcache-facebook/</link><pubDate>Mon, 07 Jul 2025 14:03:00 +0000</pubDate><guid>http://localhost:1313/scaling-memcache-facebook/</guid><description>&lt;p>What Facebook&amp;rsquo;s Memcache Taught Me About Systems Thinking&lt;/p>
&lt;blockquote>
&lt;p>&amp;ldquo;The probability of reading transient stale data is a tunable parameter&amp;rdquo;. - Scaling Memcache at Facebook (NSDI, 2013)&lt;/p>&lt;/blockquote>
&lt;p>There&amp;rsquo;s a moment in every engineer&amp;rsquo;s life when a seemingly simple component like a cache, suddenly becomes the most complex piece in the stack. For me, that moment arrived reading Facebook&amp;rsquo;s paper on scaling Memcache.
I didn&amp;rsquo;t expect a key-value store to challenge my understanding of systems architecture. But this paper wasn&amp;rsquo;t about cache keys or TTLs. It was about what happens when infrastructure hits the limits of scale, physics, and human reliability.&lt;br>
What follows isn&amp;rsquo;t a summary. It&amp;rsquo;s a set of systems insights that stayed with me, principles that go deeper than code and that I now see everywhere.&lt;/p></description></item></channel></rss>