CSE Roadmap

Specialist tier · about 2 hours · 5 parts

Part 4 of 5 · 2 min read

What CAP does not say

CAP says nothing about performance, nothing about ordinary operation with no partition, and nothing about every kind of consistency guarantee a system might offer.

What CAP does not say

Think of a weather forecast's warning about what happens specifically during a storm. It says nothing useful about an ordinary clear day. Treating the storm warning as a description of every single day would be a misreading of what the forecast actually covers.

In plain words: the CAP theorem says nothing about a system's latency or throughput, since it is a statement purely about consistency and availability during a partition, not a statement about speed. It also says nothing about how the system behaves when no partition is occurring, which is most of the time for a well-run system, so a system can be both consistent and available during ordinary operation and only face the CAP trade-off during the rare windows when an actual partition happens. Finally, CAP uses a specific, strict definition of consistency, and a system offering a weaker consistency guarantee, such as the eventual consistency covered in the replication level, is making a different, more nuanced trade-off than the simple binary CAP describes.

A worked example. A system that is both consistent and available 99.9% of the time, and briefly sacrifices one or the other only during the rare moments an actual network partition occurs, is behaving exactly as CAP predicts, not violating anything the theorem actually claims.

The key lines. No new SQL; distinguishing what a theorem does and does not constrain is a conceptual exercise, relevant when evaluating a vendor's or a colleague's claims about a system's guarantees.

Remember this

CAP is a narrow claim about one specific moment, an actual network partition, not a permanent, standing trade-off a system must advertise at all times. Treat any summary that ignores this narrowness with suspicion.

Quick notes

  • CAP applies specifically during an actual network partition, not to a system's behavior at all other times.
  • "Choose two of three" overreaches, since partition tolerance is not optional and the trade-off is not a permanent, standing choice.
  • A system can be both consistent and available during ordinary operation with no partition occurring.
  • CAP says nothing about latency or throughput; it is purely about consistency versus availability during a partition.
  • CAP's definition of consistency is strict; a system offering weaker guarantees, like eventual consistency, makes a more nuanced trade-off.