
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Rambling Me</title>
      <link>https://www.rambling-me.com/blog</link>
      <description>A blog to reflect my thoughts, learnings, and observations</description>
      <language>en-us</language>
      <managingEditor>me@rambling-me.com (Dopeking)</managingEditor>
      <webMaster>me@rambling-me.com (Dopeking)</webMaster>
      <lastBuildDate>Mon, 20 Jul 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.rambling-me.com/tags/bottlenecks/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.rambling-me.com/blog/posts/technology/scaling/orders-of-magnitude/2-what-breaks-and-when</guid>
    <title>Scaling: What Breaks, and When</title>
    <link>https://www.rambling-me.com/blog/posts/technology/scaling/orders-of-magnitude/2-what-breaks-and-when</link>
    <description>A walk up the orders of magnitude with one system. At hundreds of requests per second a single box is fine. At thousands, caching and replicas earn their keep. At tens of thousands the sync path cracks and state becomes the enemy. At millions, physics starts dictating the architecture. What breaks first at each rung, and the cheapest thing that fixes it.</description>
    <pubDate>Mon, 20 Jul 2026 00:00:00 GMT</pubDate>
    <author>me@rambling-me.com (Dopeking)</author>
    <category>technology</category><category>scaling</category><category>orders-of-magnitude</category><category>system-design</category><category>bottlenecks</category><category>database</category><category>sharding</category><category>practitioner</category>
  </item>

    </channel>
  </rss>
