Consistent Hashing, Replication & Redundancy - How Distributed Systems Scale
What happens when you add or remove a server from a distributed system? Without consistent hashing, the answer is chaos.
What happens when you add or remove a server from a distributed system? Without consistent hashing, the answer is chaos.
What’s in the video (7m 38s)
- 0:00 — Consistent Hashing, Replication and Redundancy
- 0:34 — Scalability and Reliability
- 0:51 — What is Scalability?
- 1:09 — What is Reliability?
- 1:28 — What is Consistent Hashing?
- 3:58 — Replication and Redundancy
- 4:12 — What is Redundancy?
- 4:50 — What is Replication?
- 5:33 — Active-Passive High Availability vs Active-Active High Availability
- 5:49 — Building For Fault Tolerance
Resources
- Full System Design series: YouTube playlist
- Previous episode: https://youtu.be/xoh6jYqPdek
- Next episode: https://youtu.be/UDTxRuzPOdA
For more in this series, visit the #system-design tag page or jump to the channel uploads list for everything else.
Related posts
How to Crack Any System Design Interview — Full Beginner's Guide
Most candidates fail system design interviews not because they lack knowledge — but because they don't have a clear framework to structure their thinking.
Design a Scalable System from Scratch — Full Blueprint (System Design #15)
You've learned the pieces. Now let's put them all together and design a real scalable system from scratch — the way it's done in interviews and in production.
Monolith vs Microservices - Which Architecture Should You Choose? (System
Microservices are everywhere - but are they always the right choice? Spoiler: most teams adopt them too early, and it costs them.