Course contentsShow
← System Design
Lesson 365 of 1,91910. NoSQL: Key-Value StoresFree lesson

Tunable Consistency with Quorum Reads and Writes

Understanding R, W, and N parameters for balancing consistency, availability, and performance.

Tunable Consistency with Quorum Reads and Writes

What you'll learn: How distributed key-value stores let you balance consistency, availability, and performance using configurable read and write parameters.

The Core Idea

In distributed key-value stores with replication, you don't have to choose between "always consistent" or "always available." Instead, you can tune your consistency guarantees using three parameters:

  • N = total number of replicas
  • W = number of replicas that must acknowledge a write
  • R = number of replicas that must respond to a read

These parameters work together to give you control over the trade-off between consistency and availability.

How Quorum Works

The magic formula is: R + W > N

When this condition holds, your reads and writes overlap—at least one replica that participated in the write will be consulted during the read, guaranteeing you'll see the latest data.

Example: With N=3, W=2, R=2:

  • Writes succeed when 2 out of 3 replicas acknowledge
  • Reads query 2 out of 3 replicas
  • Since 2+2 > 3, at least one replica is always "fresh"

Tuning for Different Scenarios

  • Strong consistency: Set R + W > N (e.g., R=2, W=2, N=3)
  • Fast writes, slower reads: Set W=1, R=N (write to one, read from all)
  • Fast reads, slower writes: Set W=N, R=1 (write to all, read from one)
  • Balanced: Set W=N/2+1, R=N/2+1 (majority on both sides)

The Trade-off

Lower W or R means faster operations and higher availability (fewer replicas needed), but weaker consistency guarantees. Higher values mean stronger consistency but reduced availability if replicas fail.

Key Takeaway: Tunable consistency using R, W, and N parameters lets you configure exactly how many replicas must participate in reads and writes, allowing you to optimize for your specific consistency, latency, and availability requirements.