He traces these patterns through real code. He shows you exactly how etcd uses a Lease to protect the leader, and how ZooKeeper uses a variant called "Temporal Ordering" (zxid) to know which node is ahead. We are currently experiencing a quiet crisis in software engineering. AI coding assistants (Copilot, Cursor) can generate CRUD apps instantly. But they cannot design a fault-tolerant log replication system. They hallucinate when asked to implement Paxos.
A principal engineer at ThoughtWorks, Joshi has done something quietly revolutionary. He hasn't invented a new database or a new consensus protocol. Instead, he has done the harder thing: he has translated the chaos of distributed systems into a language developers actually speak. unmesh joshi patterns of distributed systems
He built the . The "Gang of Four" for the Cloud Native Age If you have been a developer for more than a few years, you know the Design Patterns: Elements of Reusable Object-Oriented Software (the "Gang of Four" book). Those patterns (Singleton, Factory, Observer) gave us a shared vocabulary to talk about code. He traces these patterns through real code
These aren't abstract algorithms. They are concrete patterns with names, problem statements, solutions, and consequences. Let’s look under the hood. When you read Joshi’s work (collected on Martin Fowler’s website and in his upcoming O’Reilly book), you don't start with Byzantine Generals. You start with the gritty reality of what happens when a server dies. AI coding assistants (Copilot, Cursor) can generate CRUD
That is the legacy of Unmesh Joshi. He taught us to see the clockwork. Unmesh Joshi is a Principal Consultant at ThoughtWorks and the author of the upcoming O'Reilly book, "Patterns of Distributed Systems." His pattern catalog is available at martinfowler.com.
Unmesh Joshi has effectively written the "Gang of Four" book for distributed systems.
Enter .