mufassall

Data & storage / 8 / 11

CAP: when the link breaks

A seat-booking service runs in two data centres that copy changes to each other. When the link between them breaks, each side must choose: refuse writes and stay correct, or accept them and sort out conflicts later. How quorums make that choice automatic.

  • 14 min
  • Advanced
  • 10 steps
Writes accepted
100 %
Stale reads
0 %
Unresolved conflicts
0 /h
Replication lag
30 ms
Open in Lab
  • request
  • reply
  • redelivery
  • duplicate
  • lost

Numbers are a model scenario, not measurements

The real request

DB east → DB west

Request

REPLICATE dc-east -> dc-west
{
  "key": 1"seat:14A",
  "holder": "u_42",
  "version": 217,
  "lag_ms": 330
}
  1. key — The record that changed: seat 14A.
  2. version — Grows by one on every change. Replicas compare it to see which copy is newer.
  3. lag_ms — How far the copy is behind the original. Normally tens of milliseconds.
Course: 42 lessons
  1. 01 Foundations

    1. The life of a request
    2. Latency and throughput
    3. Napkin math
  2. 02 Scaling

    1. Scaling up vs scaling out
    2. Load balancing
    3. Stateless servers
    4. Caching
    5. CDN and edge caching
  3. 03 Data & storage

    1. SQL and NoSQL
    2. Database indexes
    3. Storage engines: B-tree and LSM
    4. Database replication
    5. Sharding
    6. Consistent hashing
    7. Unique IDs
    8. CAP: when the link breaks
    9. Consensus and leader election
    10. Transactions
    11. File uploads
  4. 04 Communication

    1. API styles
    2. Message queues
    3. Pub/sub and event logs
    4. Real-time updates
    5. Reliable callbacks
  5. 05 Reliability

    1. Redundancy and failover
    2. Rate limiting
    3. Timeouts and retries
    4. Observability
  6. 06 Architecture

    1. Microservices
    2. Service discovery
    3. Sagas and the outbox
    4. Batch vs stream
  7. 07 Security

    1. Authentication
    2. Authorization
    3. Encryption and secrets
  8. 08 Shipping

    1. Testing
    2. CI/CD: from commit to production
  9. 09 Whole systems

    1. From requirements to design
    2. Design a URL shortener
    3. Design a news feed
    4. Design a chat
  10. 10 Business processes

    1. Payment gateway