# Eric Brewer - CAP Twelve Years Later: How the "Rules" Have Changed (Highlights)  ## Metadata **Review**:: [readwise.io](https://readwise.io/bookreview/61288106) **Source**:: #from/readwise #from/reader **Zettel**:: #zettel/fleeting **Status**:: #x **Authors**:: [[Eric Brewer]] **Full Title**:: CAP Twelve Years Later: How the "Rules" Have Changed **Category**:: #articles #readwise/articles **Category Icon**:: 📰 **URL**:: [www.infoq.com](https://www.infoq.com/articles/cap-twelve-years-later-how-the-rules-have-changed/) **Host**:: [[www.infoq.com]] **Highlighted**:: [[2026-06-13]] **Created**:: [[2026-06-20]] ## Note Detect partition, enter partition mode to restrict operations, and start recovery procedure after partition. The recovery merges changes in partitions and fix mistakes which break invariants. ## Highlights - Because partitions are rare, CAP should allow perfect C and A most of the time, but when partitions are present or perceived, a strategy that detects partitions and explicitly accounts for them is in order. ([View Highlight](https://read.readwise.io/read/01kv0fsggrt04fjp3q80td5kpx)) ^1024879087 - BASE acronym (being second) is a bit more awkward: Basically Available, Soft state, Eventually consistent. ([View Highlight](https://read.readwise.io/read/01kv0fx5hga8nev7mpncktdqdm)) ^1024879215 - Thus, pragmatically, a partition is a time bound on communication. Failing to achieve consistency within the time bound implies a partition and thus a choice between C and A for this operation. ([View Highlight](https://read.readwise.io/read/01kv0g2dw7aw2k03wzevw42vf7)) ^1024879356 - The best way to track the history of operations on both sides is to use version vectors, which capture the causal dependencies among operations. ([View Highlight](https://read.readwise.io/read/01kv0gmdcpam0yh214cjfg5yt5)) ^1024880078