BASE

acronym	title	description
BA	Basic Availability	The database appears to work most of the time.
S	Soft-state	Stores don’t have to be write-consistent, nor do different replicas have to be mutually consistent all the time.
E	Eventual consistency	Stores exhibit consistency at some later point (e.g., lazily at read time).

Forfeit the C and I in ACID for availability => AciD, in favor of graceful degradation and performance.
A BASE datastore values availability (since that’s important for scale)
but it doesn’t offer guaranteed consistency of replicated data at write time.
Overall, the BASE consistency model provides a less strict assurance than ACID, data will be consistent in the future
- Read time (e.g., Riak)
- always consistent but only for certain processed past snapshots (e.g., Datomic)
The BASE consistency model is primarily used by aggregate stores