The PACELC Theorem

While the CAP Theorem provided a crucial foundational framework, system architects quickly identified a major practical limitation: CAP only describes database behavior during rare network partitions.

In production cloud environments, network partitions occur less than 0.1% of the time. In the remaining 99.9% of normal operations, the system is functioning without network partitions.

In 2012, Professor Daniel Abadi formulated the PACELC Theorem to address the critical trade-off that occurs during ordinary happy-path operation:

\textbf{If } Partitioned \implies choose Availability or Consistency;

\textbf{E}lse \implies choose Latency or Consistency.

Even when all networks and nodes are perfectly healthy, a database cannot simultaneously achieve sub-millisecond write latency and instant cross-region strong consistency, because transmitting data over physical distance takes time.

PACELC categorizes all distributed storage engines into four primary design profiles:

1. PC/EC (e.g., Google Spanner, CockroachDB, Bigtable, ZooKeeper):
   • If Partitioned: Favors Consistency (rejects writes on minority partitions).
   • Else (Normal): Favors Consistency (waits for synchronous Raft/Paxos quorum consensus across nodes before returning success to the client, accepting +20ms to +50ms latency overhead).
2. PA/EL (e.g., Apache Cassandra, Amazon DynamoDB, Couchbase, Riak):
   • If Partitioned: Favors Availability (allows independent writes on all partitions).
   • Else (Normal): Favors Latency (writes locally to in-memory MemTable and commits immediately in < 2ms, replicating asynchronously in the background).
3. PC/EL (e.g., PostgreSQL with Asynchronous Primary-Replica Replication):
   • If Partitioned: Favors Consistency (all writes must hit the primary).
   • Else (Normal): Favors Latency (read queries hit asynchronous replicas with < 1ms latency, tolerating minor replication lag).
4. PA/EC (Rare Hybrid):
   • If Partitioned: Favors Availability (serves stale reads).
   • Else (Normal): Favors Consistency (enforces synchronous quorum verification during normal operation).