Part 1 of 7 · 1 min read
Why this page follows ACID
In this module you will
- Name the race conditions that concurrent transactions can cause and recognise each in a short story.
- Say what read committed and snapshot isolation guarantee and what they leave open.
- Explain how multi-version concurrency control gives each transaction a snapshot.
- Prevent lost updates with atomic operations, explicit locks, automatic detection or compare-and-set.
- Spot write skew and phantoms and choose a safeguard.
Module 1 defined isolation as the ideal that transactions do not interfere. Real databases rarely give the ideal, because it is slow. They offer weaker levels. Each weaker level allows some bugs. A designer who knows which bugs are allowed can pick a level or add a safeguard. The tier is Core. The numbers are made up to show the idea, unless the text names a book.