<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>CQRS on wid's blog</title><link>https://wid-blog.github.io/en/tags/cqrs/</link><description>Recent content in CQRS on wid's blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 07 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wid-blog.github.io/en/tags/cqrs/index.xml" rel="self" type="application/rss+xml"/><item><title>Event Sourcing and CQRS</title><link>https://wid-blog.github.io/en/posts/tech/architecture/event-sourcing-and-cqrs/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://wid-blog.github.io/en/posts/tech/architecture/event-sourcing-and-cqrs/</guid><description>ES and CQRS address how a system&amp;rsquo;s source of truth is shaped and how its views are separated from it. Adoption cost spreads across the system, so I lean toward adopting only when the value can be stated explicitly.</description></item></channel></rss>