map / distributed-systems

Pillar 03 · 7 principles

Distributed Systems.

Everything fails, and it fails partially.

System design interviews reward people who reason from a few laws — queueing, probability, quorums — instead of reciting architectures. These are those laws.

01

Queueing & Little’s Law

Latency doesn’t grow linearly with load: as utilization approaches 100%, wait time grows without bound.

Drag utilization and watch latency explode.

Interactive →
02

Availability math

Dependencies in series multiply their availabilities down; redundant copies in parallel multiply their failure probabilities down.

Nines adding up (and draining away) through serial vs parallel dependencies.

Coming soon
03

Replication & quorums

If every read quorum overlaps every write quorum (R + W > N), a read is guaranteed to see the latest acknowledged write.

N replicas with adjustable R and W, highlighting the overlap.

Coming soon
04

Consensus (Raft)

A majority quorum means any two majorities share a member, so a cluster can agree on one leader and one log despite failures.

A step-through Raft leader election with terms, votes, and a partitioned node.

Coming soon
05

Consistency models

Consistency models are promises about which values a read may return; stronger promises cost coordination, and coordination costs latency.

The same history of reads and writes judged under linearizable, sequential, and eventual consistency.

Coming soon
06

Partitions

When the network splits, a system must choose between refusing some requests and risking divergent answers.

A cluster split in two, toggling between “stay available” and “stay consistent”.

Coming soon
07

Retries & cascades

Retries multiply load exactly when a system is weakest, so without budgets and backoff they turn a slowdown into an outage.

A retry storm amplifying load across layers, then tamed by backoff, jitter, and retry budgets.

Coming soon

How it shows up in interviews

  • System design: capacity, SLOs, and designing for failure.
  • “What happens when this dependency gets slow?”
  • Error budgets and the arithmetic behind “nines”.

Next pillar

04 · Coding

Practical code, under real constraints.

Go →