A database stores, organizes, and retrieves structured data while making defined promises about access, integrity, and reliability. Those promises create trade-offs that become more difficult to manage as data moves from one server to many. section 6.1
ACID describes a strong reliability contract commonly associated with relational databases: Atomicity, Consistency, Isolation, and Durability. Together, these properties address whether transactions are all-or-nothing, preserve valid states, remain appropriately separated, and survive failures. section 6.1.1
The core guarantees include:
- Atomicity makes a transaction all-or-nothing: if one operation fails, the database rolls back the others. section 6.1.1
- Consistency moves the database only between valid states, enforcing rules such as foreign keys, data types, and application invariants. section 6.1.1
- Isolation and Durability complete the ACID contract, alongside transactions, consensus, consistency models, and availability choices that determine how guarantees behave at scale. section 6.1 section 6.1.1
Bank transfer
A transfer deducts money from one account and adds it to another. Atomicity requires both changes to succeed together; if either step fails, neither account is updated. section 6.1.1
Beyond one database
A process that writes to a database and publishes a Kafka message may also need all-or-nothing behavior. In that case, atomicity applies to the wider system rather than only the database. section 6.1.1




























