<?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>Distributed Systems on wid's blog</title><link>https://wid-blog.github.io/en/tags/distributed-systems/</link><description>Recent content in Distributed Systems on wid's blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 09 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://wid-blog.github.io/en/tags/distributed-systems/index.xml" rel="self" type="application/rss+xml"/><item><title>Microservices Architecture</title><link>https://wid-blog.github.io/en/posts/tech/architecture/microservices-architecture/</link><pubDate>Sat, 09 May 2026 00:00:00 +0000</pubDate><guid>https://wid-blog.github.io/en/posts/tech/architecture/microservices-architecture/</guid><description>MSA is a decision about which criterion to use to decompose the system. Domain boundary, data ownership, scale pattern, failure isolation — the chosen criterion creates the service boundaries, and those boundaries decide communication and data in turn.</description></item><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><item><title>Distributed Transactions</title><link>https://wid-blog.github.io/en/posts/tech/architecture/distributed-transactions/</link><pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate><guid>https://wid-blog.github.io/en/posts/tech/architecture/distributed-transactions/</guid><description>Distributed transactions are about how a single ACID transaction decomposes across services and how its pieces are reassembled. The roles and trade-offs of 2PC, Saga (Choreography vs Orchestration), and Outbox.</description></item><item><title>Kafka Fundamentals and KRaft Mode</title><link>https://wid-blog.github.io/en/posts/tech/infra/kafka-fundamentals-kraft/</link><pubDate>Thu, 22 Feb 2024 00:00:00 +0000</pubDate><guid>https://wid-blog.github.io/en/posts/tech/infra/kafka-fundamentals-kraft/</guid><description>Core Kafka concepts (topics, partitions, consumer groups, replication) and the background behind KRaft mode, which removes the ZooKeeper dependency.</description></item></channel></rss>