AlgoPlus//databases / transactions
Read the theory

Transactions · MVCC

Two transactions, one row — multi-version concurrency lets readers and writers run without blocking.

Isolation
Repeatable Read (snapshot)
Acting
Versions
0
Isolation level
Legend
T1
T2
Committed version
Superseded version
AI Tutor Workspace
In a nutshell
A transaction groups reads and writes so they all commit together or all roll back — the heart of ACID. To let many run at once, MVCC keeps multiple versions of each row: a writer creates a new version while readers keep seeing the one their snapshot froze, so reads never block writes. The isolation level decides which version a re-read sees.
Ready
Press play to begin the cinematic walkthrough.
Instead of locking readers out, the database keeps multiple versions of each row. A writer forks a new version; readers keep seeing the one their snapshot froze — so reads and writes never block.
Key terms
Go deeper in the lesson
Read the full theory, intuition & complexity for Transactions · MVCC.