Paths/Backend Engineer/Relational Databases / Migrations & Transactions
Pick the Right Isolation Level
Isolation levels trade correctness for concurrency. Write the policy for each workload and name the anomaly each one prevents.
Validator
⏱ 0:00
IDLE — checks run live as you type commands; submit when done
01Requirements
live checks- File ~/backend/db/isolation.md exists○
- The document maps the workloads to isolation levels○
- The document names the anomalies the levels prevent○
02Walkthrough
1 of 3 revealed- 01
Write the workload mapping
Read committed is the default for ordinary reads. Repeatable read is for reports that must not see a half-finished state.
echo '# Isolation levels\n\n## Workloads\n\n- order lookup: READ COMMITTED\n- financial report: REPEATABLE READ' > ~/backend/db/isolation.md - 2 locked · each failed submit reveals one
03Stuck?
0 of 3 revealedTake a hint without losing the lab — each one points at the thing to look at, not at the answer.
04AI Tutor
guides, never solvesTell me what you're stuck on — I'll nudge, not solve. Which requirement are you looking at?
04Notebook
saved locally in this browserlearner@lab — ubuntu:24.04
Session is disposable
↑/↓ recalls commands · Ctrl+Enter submits · type help for the command list