Medium👤 3-5 years👤 8-15 years 1 min read

Strong vs eventual consistency, and how do quorums (R+W>N) tune it?

Asked inAmazonGoogleMicrosoftbanking
#consistency#quorum#eventual#strong#replication
Report issue

⚡ Short Answer

Strong consistency: every read sees the latest write (simpler reasoning, lower availability/higher latency). Eventual: replicas converge over time (higher availability/scale, stale-read window). Quorum systems tune it: with N replicas, requiring R+W>N reads/writes guarantees overlap and read-your-writes.

Coffee Chat Question

Concept Made Simple

Strong vs eventual consistency, and how do quorums (R+W>N) tune it?

🧠Mind Map Answer

Remember It Faster

Strongalways latest, lower availability
Eventualconverges, stale window, scalable
QuorumR + W > N → overlap = fresh reads
Choiceper data criticality

🔥What If?

Think Beyond the Expected

With N=3 replicas, why does W=2, R=2 give consistent reads while W=1, R=1 doesn't?

R+W>N (2+2>3) forces the read set and write set to overlap on at least one replica that has the latest value, so a read sees the newest write. W=1,R=1 (1+1<3) can read a replica that missed the write → stale. Quorum sizing is the knob between consistency and availability/latency.

😂Real World

Dynamo-style stores (Cassandra) expose tunable R/W quorums so you choose consistency vs latency per query; picking consistency by data criticality (money = strong, feed = eventual) is the design skill.

🎯Interviewer's Expectation

Keywords they're listening for:

strong vs eventual trade-offsquorum R+W>Noverlap = fresh readper-data choiceavailability/latency cost

⚠️Common Mistakes

  • Assuming eventual = 'sometimes wrong forever'
  • Strong consistency everywhere (availability/latency hit)
  • Misunderstanding quorum math

Best Practices

  • Tune R/W quorums per query need
  • Strong for money/inventory; eventual for feeds
  • Design for the stale-read window

🔁Follow-up Questions

  • 1How does Cassandra's tunable consistency work?
  • 2What is read-repair / anti-entropy?
  • 3When is strong consistency worth the cost?

🧩Related Technologies

CassandraDynamoDBquorumread-repair

Continue Learning with AI

Take this question deeper with your favourite AI assistant. Pick a depth, copy the prompt, or open it directly — AI is your learning companion, not a shortcut.

Plain-language foundations

I'm preparing for a software engineering interview and want to understand this from scratch, as a beginner.

Topic: Databases (System Design)
Interview question: "Strong vs eventual consistency, and how do quorums (R+W>N) tune it?"

Please:
1. Explain the core idea in simple, plain language, using an everyday analogy.
2. Define any technical terms you use.
3. Walk through one small, concrete example.
4. Finish with a single sentence I can easily remember.

Keep the tone friendly and assume I'm new to this topic.
Open inChatGPTGeminiClaude

Was this answer helpful?

Support our platform by exploring our recommended products.

As an Amazon affiliate, purchases through these links may earn us a small commission — at no extra cost to you. It helps keep Full Stack Interview Guru free.

Related Questions