Consistent Hashing 101
Why adding a server shouldn't ruin your entire cache.
I’ve been shipping distributed systems for about a decade — and I still open a fresh tab to remind myself how consistent hashing works. So I write it down here: distributed systems, networking, and cryptography, explained the way I wish they’d been explained to me. I try to stay honest about what I actually understand, which is why every post carries a confidence rating. New here? Start with the CAP series →
Why adding a server shouldn't ruin your entire cache.
Three ways to keep copies of your data, and the trade-offs of each.
A look at one of the most interesting engineering decisions behind one of the largest single-primary PostgreSQL deployments in the world.
New here? This is the best way to read the blog.
Why most systems live between CP and AP and how to choose where yours belongs.
How DynamoDB, Cassandra, and DNS stay available during network failures—and how they clean up the mess afterward.
Let's look at what CP systems actually do under the hood when they choose consistency over availability.
Let's get to the bottom of what Consistency, Availability, and Partition Tolerance actually mean in production distributed systems.
Browse all 15 essays →Series: CAP (4) · Merkle (2)RSS
No schedule I'm religious about. No tracking. Unsubscribe with one click.