<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Event Sourcing on App Coding</title>
    <link>https://appcoding.com/tags/event-sourcing/</link>
    <description>Recent content in Event Sourcing on App Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 05 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://appcoding.com/tags/event-sourcing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Kafka for One Machine: An Embedded Event Log With Offsets, Compaction and No Broker</title>
      <link>https://appcoding.com/kafka-for-one-machine-an-embedded-event-log-with-offsets-compaction-and-no-broker/</link>
      <pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/kafka-for-one-machine-an-embedded-event-log-with-offsets-compaction-and-no-broker/</guid>
      <description>&lt;p&gt;A desktop app wants an undo history that survives a crash. An edge gateway buffers sensor readings while its uplink is down and has to replay them, in order, once the link is back. An AI agent writes down every action it takes so a bad run can be replayed later. All three are the same data structure: an append-only sequence of records, plus readers that remember where they stopped. Kafka is that structure, and also a cluster, partitions and the people who tune them.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
