BASE
Design for availability with temporary state and eventual convergence.
Use this when A non-critical projection can stay usable while updates propagate.
without the term
“The read model can lag, but it must catch up reliably. Define what temporary differences we accept.”
with the term · How do you ask a model for BASE?
Define the BASE behavior for this projection: acceptable staleness, convergence, and invariants that must stay atomic.
What is BASE?
BASE expands to Basically Available, Soft state, and Eventually consistent. It describes a design approach that permits temporary differences and reconciliation, not one precise transaction isolation level.
Why does BASE matter when vibe coding?
An agent can use the acronym to excuse permanent missing updates or broken payment invariants.
How do you do BASE?
Name the data that may lag, how it converges, and what still requires atomic changes. Check delayed, duplicate, and failed updates against those rules.
What goes wrong with BASE?
An eventually updated view can coexist with ACID transactions. Product categories do not establish exact guarantees.
Sources for this entry
- AWS: ACID and BASE
The BASE acronym and the use of eventual convergence. Product labels alone do not define transaction guarantees.
- Amazon DynamoDB: Read consistency
Strongly consistent reads reflect successful prior writes within the supported read scope; eventual reads may lag.
Sources checked . Source checks do not establish human editorial approval. How we check content.