ACID Properties
Updated 2026-08-02
INTRODUCTION
English translation pending.
CORE DEFINITION
ACID names four guarantees that database transactions must provide: atomicity, so a transaction completes fully or not at all; consistency, so constraints hold before and after; isolation, so concurrent transactions do not interfere; and durability, so committed results survive failure. The framework was formalized in the 1980s around relational transaction processing and remains the benchmark against which weaker guarantees such as eventual consistency are judged.
SCAFFOLDING EFFECT
Reduce cognitive load
- Set a hard standard: ask whether a promise can be partially fulfilled, which would break atomicity - Probe for wavering: ask whether the commitment can be revoked midway, which would break durability - Compare soft promises: label anything weaker as eventual consistency rather than a guarantee
Anchor fast decisions
The four properties together make a group of operations behave as one indivisible step. Atomicity rolls back partial work, consistency preserves declared constraints, isolation prevents concurrent transactions from observing each other's intermediate state, and durability writes committed results to stable storage. Without all four, failures leave data in states no rule permits.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/ACIDverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS