Part 1 of 5 · 1 min read
Why this page comes first
In this module you will
- Match a specific application bug to the anomaly, and therefore the isolation level, that prevents it.
- Explain why defaulting to the strictest isolation level everywhere is usually the wrong call.
- Decide between relying on the database's isolation level and adding an explicit application-level check.
- Walk through a decision process for choosing isolation level on a new feature.
This level has covered ACID, serializability, several concurrency control protocols, and the specific anomalies each one does or does not prevent. This closing page turns that into a practical decision process. Which guarantee does a specific feature actually need, and what does reaching for more than that actually cost?