<?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 Scholion</title><link>https://scholion.thluiz.com/tags/event-sourcing/</link><description>Recent content in Event-Sourcing on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Wed, 23 Sep 2026 14:48:46 +0100</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/event-sourcing/index.xml" rel="self" type="application/rss+xml"/><item><title>33/60 Days System Design Questions</title><link>https://scholion.thluiz.com/notes/33-60-days-system-design-questions/</link><pubDate>Wed, 23 Sep 2026 14:47:00 +0100</pubDate><guid>https://scholion.thluiz.com/notes/33-60-days-system-design-questions/</guid><description>A daily.dev system design prompt: an order service that only stores current state can&amp;rsquo;t reconstruct a billing dispute, and the post argues event sourcing is the real fix, not a patch.</description></item></channel></rss>