Two of three, and what that means for a blockchain. This lesson sits inside Module II — Consistency — of Databases, the course that anchors the Blockchain Foundations program. It is not a survey; it is the specific, working understanding of "CAP theorem" that the rest of the course assumes you carry forward.
- 01Define CAP theorem in the precise sense used across Databases.
- 02Recognize when CAP theorem is the correct lens for the situation in front of you, and when it is not.
- 03Apply CAP theorem to a concrete case drawn from Consistency, and defend the result in plain language.
- 04Connect CAP theorem to the adjacent lessons in this module without collapsing the distinctions between them.
The idea, stated plainly
Two of three, and what that means for a blockchain. That single sentence is the whole lesson in compressed form. The rest of the reading unfolds it — what it means when the terms are taken seriously, where it comes from, and what work it does inside Databases. Read the sentence, then read it again after the sections below; it should carry more weight the second time.
Why it belongs in Consistency
Module II exists because the tradeoffs the cap theorem forces. "CAP theorem" is one of the pillars of that module: without it, the later lessons either become memorization or lose their bite. Notice which earlier lessons this one leans on, and which later lessons will lean on it — the shape of the module is easier to see once you place this piece.
How the School of Blockchain faculty use it
In practice, working school of blockchain professionals reach for this idea before they reach for a formula or a tool. It is a way of framing the problem so that the right question comes first. The mark of understanding is not that you can recite CAP theorem; it is that you catch yourself using it, unprompted, when the situation calls for it.
Common misreadings
The most frequent error is to treat CAP theorem as a slogan and skip the mechanics. The second most frequent is the opposite — treating the mechanics as the point, when the mechanics are only there to make the idea usable. Both errors collapse the same distinction, and both are correctable by returning to the one-line summary and asking what it actually claims.
A single-panel schematic. The center holds the phrase "CAP theorem". Four short lines radiate out to labels drawn from the module: the situation, the actors, the mechanism, and the constraint. The figure is meant to be redrawn by hand in under a minute.
A horizontal spine labeled with the module's lessons in order. The current lesson is marked; arrows point to the lessons immediately before and after it, indicating the direction of dependency. The visual makes the sequencing choices explicit.
A two-column diagram. The left column shows the concept as it is often misread — flattened into a slogan. The right column shows the same concept as Databases uses it, with the operational content restored. The gap between the columns is the lesson.
- CAP theorem is a working tool, not a slogan.
- Its meaning is set by the module it lives in: Consistency.
- Understanding is demonstrated by unprompted use in the correct situation.
- The adjacent lessons in this module are its natural context; read them together.
- 104 — Databases, Module II: Consistency — The parent module for this lesson. Re-read the module blurb after finishing the lesson.
- The Anabasis Academy — School of Blockchain, Blockchain Foundations — The wider program this lesson serves; the Certificate in Blockchain Foundations (Foundation tier). credential ultimately certifies mastery of ideas like this one.