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 .
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
Or consider How do you know a value is committed? You don't need a leader to tell you. If a majority of nodes (N/2+1) acknowledge a write, you have a quorum. It is the mathematical bedrock of consensus. You are watching a recover via a Leader
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 has given us a lens
Unmesh Joshi has effectively written the "Gang of Four" book for distributed systems.
In the modern era of software engineering, we speak in superlatives. We boast about systems that span continents, handle millions of requests per second, and achieve "five-nines" of availability. Yet, for most engineers, the internals of these systems remain a black box—a magical realm of consensus algorithms, replication logs, and failure detectors.
His core thesis is simple but profound: