What CAP doesn't cover
Take one year of KataTube. The link was down three times, for under an hour in all. For the rest of the year every message arrived.
The theorem's choice arises in those minutes and at no other time. It is a statement about two exact promises, CAP's consistency and CAP's availability, under one fault, a partition, and only while it lasts. Most questions about a store fall outside it:
- How fast is it? CAP says nothing about , the time a request takes. A store that needs two seconds for every answer is no less consistent or available.
- What does a store that answers during a cut still promise? CAP does not say. It may keep weaker guarantees, or none.
- What about the rest of the year? While every reply arrives before its timeout, nothing in CAP stops a store from being consistent and available together.
PACELC adds the half CAP leaves out: with no partition, a store still trades latency against consistency.
CAP's two words are also all or nothing. Real stores offer a range of guarantees between “consistent” and none at all, and their availability is a share, of time or of requests, not a yes or no.
CAP is about two exact promises and one fault, and only while that fault lasts: it says nothing about speed, weaker guarantees or a healthy network.