Part 1 of 5 · 1 min read
Why this page comes first
In this module you will
- Define a dirty read, a non-repeatable read, and a phantom read as concrete anomalies.
- State which of these three anomalies each standard isolation level prevents.
- Pick the right isolation level for a scenario based on which anomaly matters.
- Explain why a stricter isolation level is not always the right default choice.
The previous page defined serializability in the abstract, as a property of a schedule. Real databases offer a small menu of named isolation levels, each allowing a specific set of anomalies in exchange for better concurrency. This page names those anomalies concretely, then matches each isolation level to exactly what it prevents.