<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sagas on Nalar</title>
    <link>https://nalar.dev/tags/sagas/</link>
    <description>Recent content in Sagas on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 22 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/sagas/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Saga Compensation Is Not Transaction Rollback</title>
      <link>https://nalar.dev/saga-compensation-is-not-transaction-rollback/</link>
      <pubDate>Tue, 22 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/saga-compensation-is-not-transaction-rollback/</guid>
      <description>&lt;h1 id=&#34;saga-compensation-is-not-transaction-rollback&#34;&gt;Saga Compensation Is Not Transaction Rollback&lt;/h1&gt;&#xA;&lt;p&gt;A multi-service operation can cross inventory, payments, shipping, and other independently committed systems. Once one service commits its step, a later failure cannot make that earlier commit disappear through an ordinary database rollback.&lt;/p&gt;&#xA;&lt;p&gt;A saga handles this boundary by pairing forward actions with explicit recovery actions. If a later step fails, the coordinator invokes compensations for earlier completed steps where the business process permits them.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
