
  <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, 10 Aug 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.rambling-me.com/tags/outbox/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.rambling-me.com/blog/posts/technology/scaling/api-backend/4-correctness-in-an-async-world</guid>
    <title>Scaling the API: Correctness in an Async World</title>
    <link>https://www.rambling-me.com/blog/posts/technology/scaling/api-backend/4-correctness-in-an-async-world</link>
    <description>The hard part nobody warns you about. Once you go asynchronous and at-least-once, duplicates, retries, partial failures, and the dual-write problem all become your problem. The toolkit: idempotency as the foundation, retries with dead-letter queues, the outbox pattern for atomic publish, and sagas for multi-step flows like payment. Where a bank and a food app draw the line differently.</description>
    <pubDate>Mon, 10 Aug 2026 00:00:00 GMT</pubDate>
    <author>me@rambling-me.com (Dopeking)</author>
    <category>technology</category><category>scaling</category><category>api-backend</category><category>idempotency</category><category>outbox</category><category>saga</category><category>dead-letter-queue</category><category>practitioner</category>
  </item>

    </channel>
  </rss>
