
  <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>Wed, 29 Jul 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.rambling-me.com/tags/async/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.rambling-me.com/blog/posts/technology/scaling/api-backend/2-where-sync-breaks</guid>
    <title>Scaling the API: Where Sync Breaks, and the Broker Enters</title>
    <link>https://www.rambling-me.com/blog/posts/technology/scaling/api-backend/2-where-sync-breaks</link>
    <description>The point where synchronous request-response stops being enough, and the honest case for a message broker like Kafka. The good reasons are decoupling, load-leveling, fan-out, and durability. The bill is eventual consistency, added latency, operational burden, and harder debugging. And a clear account of when you should not reach for it at all.</description>
    <pubDate>Wed, 29 Jul 2026 00:00:00 GMT</pubDate>
    <author>me@rambling-me.com (Dopeking)</author>
    <category>technology</category><category>scaling</category><category>api-backend</category><category>system-design</category><category>kafka</category><category>event-driven</category><category>async</category><category>practitioner</category>
  </item>

  <item>
    <guid>https://www.rambling-me.com/blog/posts/technology/scaling/orders-of-magnitude/3-the-menu-of-levers</guid>
    <title>Scaling: The Menu of Levers</title>
    <link>https://www.rambling-me.com/blog/posts/technology/scaling/orders-of-magnitude/3-the-menu-of-levers</link>
    <description>The full survey of everything you can reach for when you need to scale, on both sides of the wire. API-side levers from horizontal scale and caching to async and backpressure, and client-side levers from the CDN to optimistic UI. Each one gets a line on what it buys and what it costs. This is the map; the API and UI series are the territory.</description>
    <pubDate>Wed, 22 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>caching</category><category>load-balancing</category><category>async</category><category>practitioner</category>
  </item>

    </channel>
  </rss>
