Skip to main content
PreparationZone Logo
PrepZone

CAP Theorem and PACELC

Why you cannot have perfect consistency, availability and partition tolerance at once.

Pass checkpoint below

CAP theorem basics

Consistency — every read returns the latest write or an error. Availability — every request receives a non-error response (not necessarily the latest data). Partition tolerance — the system continues despite network splits between nodes.

Consistencyevery read = latest write
Availabilityevery request gets a response
Partition tolerancenetwork splits happen

CP systems: bank ledgers. AP systems: social feeds, DNS.

During a network partition, pick consistency or availability — not both.

In practice, partitions happen. The real choice is CP (refuse writes/reads until consistent) vs AP (serve possibly stale data).

CP vs AP examples

AspectCP (Consistency + Partition tolerance)AP (Availability + Partition tolerance)
Behaviour during partitionReject requests or blockServe from local replica
ExamplesZooKeeper, etcd, traditional RDBMS primaryCassandra, DynamoDB (configurable)
Good forLeader election, inventory locksSocial feeds, analytics, session store
RiskDowntime during partitionStale reads, merge conflicts
  • Behaviour during partition

    CP (Consistency + Partition tolerance)Reject requests or block
    AP (Availability + Partition tolerance)Serve from local replica
  • Examples

    CP (Consistency + Partition tolerance)ZooKeeper, etcd, traditional RDBMS primary
    AP (Availability + Partition tolerance)Cassandra, DynamoDB (configurable)
  • Good for

    CP (Consistency + Partition tolerance)Leader election, inventory locks
    AP (Availability + Partition tolerance)Social feeds, analytics, session store
  • Risk

    CP (Consistency + Partition tolerance)Downtime during partition
    AP (Availability + Partition tolerance)Stale reads, merge conflicts

The rest of this guide is part of Pro

Free covers every fresher guide in full. Pro unlocks Senior, Staff and Architect guides across every track.

Still to come · 5 sections

  • PACELC extension
  • Consistency models in practice
  • Choosing for your product
  • Handling partitions in design
  • Common misconceptions

Test yourself

Answer these before moving on — recall is what makes it stick.