ACID

ACID Explained

1. Atomicity

All operations within a transaction must succeed or all should be undone (rollback).
If any step fails (e.g. inserting into one table fails), the entire transaction is rolled back.

1. Consistency

Transactions must take the database from one valid state to another, respecting all constraints, triggers, cascades, etc. Invalid data should never slip in.

1. Isolation

Concurrent transactions should not see each other’s intermediate (uncommitted) states.
This prevents issues like dirty reads, nonrepeatable reads, phantom reads.

1. Durability

Once a transaction is committed, its result must persist even in the face of crashes, power loss, or system failures.

✅ Summary

Atomicity → all or nothing

Consistency → valid state transitions

Isolation → no interference between concurrent TXs

Durability → committed data survives failures

By following these principles, DBMS remain robust, reliable, and safe—especially in high concurrency / fault-prone environments like financial systems