<?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 Pi Stack</title>
    <link>https://www.pistack.xyz/tags/event-sourcing/</link>
    <description>Recent content in Event-Sourcing on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 03 May 2026 12:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/event-sourcing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted CQRS Platforms — Axon Server vs EventStoreDB vs Apache Kafka 2026</title>
      <link>https://www.pistack.xyz/posts/2026-05-03-axon-server-vs-eventstoredb-vs-kafka-self-hosted-cqrs-platforms-guide/</link>
      <pubDate>Sun, 03 May 2026 12:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-03-axon-server-vs-eventstoredb-vs-kafka-self-hosted-cqrs-platforms-guide/</guid>
      <description>&lt;p&gt;The Command Query Responsibility Segregation (CQRS) pattern separates read and write operations in your application, optimizing each for its specific use case. When combined with event sourcing — storing state changes as an immutable sequence of events — CQRS becomes a powerful architecture for complex domains, audit-heavy applications, and systems that need to replay or reconstruct state over time.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
