<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Transactional Outbox on Nalar</title>
    <link>https://nalar.dev/tags/transactional-outbox/</link>
    <description>Recent content in Transactional Outbox on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 20 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/transactional-outbox/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Transactional Outbox Keeps Database State and Events Aligned</title>
      <link>https://nalar.dev/transactional-outbox-keeps-database-state-and-events-aligned/</link>
      <pubDate>Sun, 20 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/transactional-outbox-keeps-database-state-and-events-aligned/</guid>
      <description>&lt;p&gt;A service often needs one operation to change database state and emit an event. An order may move to &lt;code&gt;paid&lt;/code&gt; while &lt;code&gt;OrderPaid&lt;/code&gt; must reach a message broker. Those two writes cross different systems, so a normal database transaction cannot make both commits atomic.&lt;/p&gt;&#xA;&lt;p&gt;Writing the database first leaves a gap: the process can stop after commit but before publishing. Publishing first creates the opposite gap: consumers can observe an event for a database change that later fails.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
