ChaptersTransactions
Transactions
How do you let many things change data at once without corrupting it?
Not started
Transactions & Isolation
Two requests that are each correct can still corrupt your data when they run at the same time. Transactions promise to stop that, but most databases, by default, only keep part of the promise. Here's exactly which part.
Serializability
The only isolation level with no anomalies to memorise. Databases get there in three very different ways, by running one transaction at a time, by locking, or by letting everything run and checking afterwards, and each one fails in its own way.
Distributed Transactions
One write, two machines, and a promise that both or neither will change. How two-phase commit keeps that promise, why it blocks, how consensus fixes the blocking, and what to do instead when you can't afford it.