ACID Properties in DBMS: Atomicity, Consistency, Isolation, and Durability
ACID is a set of four properties that guarantee reliable processing of database transactions, even in the event of errors, power failures, or concurrent access by multiple users.
The Four ACID Properties
- Atomicity — a transaction is treated as a single indivisible unit; it either completes fully or not at all. If any part fails, the entire transaction is rolled back.
- Consistency — a transaction takes the database from one valid state to another, ensuring all rules, constraints, and triggers are respected.
- Isolation — concurrent transactions execute as though they were run one after another, preventing them from interfering with each other's intermediate results.
- Durability — once a transaction is committed, its changes are permanently saved, even if the system crashes immediately afterward.
Real-World Example: Bank Transfer
Imagine transferring ₹5,000 from Account A to Account B. This involves two steps: debit A, then credit B.
| ACID Property | Role in This Transaction |
|---|---|
| Atomicity | If the credit step fails, the debit is also rolled back — money isn't lost |
| Consistency | Total balance across both accounts remains mathematically correct |
| Isolation | Another transaction checking balances won't see a half-completed transfer |
| Durability | Once confirmed, the transfer survives even a server crash |
Why ACID Matters
ACID compliance is critical for systems where data accuracy is non-negotiable, such as banking, healthcare, and e-commerce order processing. Most traditional relational databases like MySQL (InnoDB), PostgreSQL, and Oracle are fully ACID-compliant by design.
Understanding ACID properties naturally leads into the broader topic of transactions, which is where these guarantees are actually implemented and enforced.
Ready to master DBMS & SQL Training Course?
Join Uncodemy's hands-on training with mentor support and placement assistance.