Unmesh Joshi has effectively written the "Gang of Four" book for distributed systems.
When the "Patterns of Distributed Systems" book is finally released (expected late 2026/early 2027), it will sit on the desk of every infrastructure engineer, right between Designing Data-Intensive Applications (Kleppmann) and Site Reliability Engineering (Google). Unmesh Joshi has done for distributed systems what Christopher Alexander did for architecture and what the Gang of Four did for OOP. He has given us a lens. unmesh joshi patterns of distributed systems
Enter .
You are watching a recover via a Leader and Followers pattern, using a High-Water Mark to truncate a Write-Ahead Log , protected by a Lease and a Generation Clock . Unmesh Joshi has effectively written the "Gang of
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. He has given us a lens
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.
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.