Explain quorum-based consistency.
Skip to solutionKEEP THE
hardSystem Design
What is a read/write quorum?
112 views
01
Understand the problem
quorumconsistency
02
Attempt it yourself
Sketch your approach before reading the solution — that's what interviews test.
Nudge consolestandby
Stuck? Beam a request up — the console returns a conceptual nudge that guides your logic without spoiling the implementation.
03
Study the solution
Step 1: Outline use cases and constraints
Gather requirements and scope the problem. Ask questions to clarify use cases and constraints. Discuss assumptions.
Use cases
We'll scope the problem to handle only the following use cases
- User needs to understand
quorumto make architecture decisions
Solution ready — 2 min read
Classified // press E to declassify
04
Read the code
Quorum write + read
Run PlaygroundN, W, R = 5, 3, 3 # W + R > N guarantees overlap
replicas = [{"value": None, "version": 0} for _ in range(N)]
def write(value, version):
acks = 0
for r in replicas: # send to all, succeed once W ack
r["value"], r["version"] = value, version
acks += 1
if acks == W:
break
return acks >= W
def read():
sample = replicas[:R] # read from R replicas
latest = max(sample, key=lambda r: r["version"]) # newest wins
return latest["value"], latest["version"]
write("v2", 2)
print("read ->", read()) # sees v2 because the read/write sets overlap05
Join the discussion
Discussion (0)
Sign in to join the discussion.
No responses yet. Be the first to share what you think.
Transmission complete // awaiting log
KEEP THE
STREAK ALIVE.
Dossier 82 of 99 decoded in the System Design track. One more won't hurt.