intermediate · cohort
Transaction Isolation in Practice
5 weeks · 6 hrs/week
Isolation levels sound abstract until money moves. You will reproduce anomalies in a safe sandbox, then refactor application code to reduce risk without over-locking.
What ships in this outline
- Runnable repro cases for common anomalies
- Mapping ORM session defaults to database behavior
- Design exercises for idempotency keys
- Short lectures on MVCC intuition
- Pair review of transaction boundaries
- Capstone: incident-style postmortem write-up
Outcomes
- Choose isolation defaults for three service archetypes
- Diagram where your app holds locks longer than necessary
- Propose a test that catches a regression early
Lead mentor
Haruto Watanabe
Former data platform lead at a logistics SaaS; PostgreSQL contributor talks in Tokyo.
FAQ
SQL Foundations or equivalent comfort with transactions and migrations.
Examples skew TypeScript/Node and Go; patterns apply broadly.
Distributed transactions across unrelated vendors are referenced but not implemented end-to-end.
Experience notes
“Finally understood why our “retry” made double posts. The idempotency lab should be mandatory.”
“Dense material — weekend blocks helped. Would like one more async quiz mid-course.”