Intermediate
Transactions and Isolation
Move beyond textbook definitions with reproducible anomalies in controlled branches. You will practice choosing isolation levels with explicit invariants and documenting failure modes for support teams.
Duration: 3 weeks · 26 hours · Format: Intensive evening blocks (JST-friendly)
Price (informational): ￥142,000
Request information
What is included
- Repro scripts for phantom reads vs your domain rules
- Advisory locks for queue-like workflows
- Retry budgets with jitter policies
- Designing idempotency keys with database backing
- Readable transaction boundaries in services
Outcomes
- Pick an isolation default with a written decision record
- Ship a retry policy that survives duplicate POST storms
- Explain predicate lock contention to a product manager
Lead contact
Leo Park
Payments infrastructure background; teaches transaction semantics cohorts.
FAQ
Primary facilitation in English with JP breakout rooms twice per week.
Examples are Postgres-first; a short appendix maps differences.
We do not certify you for PCI audits — content is educational only.
Participant notes
Serializable sandbox scripts mirrored our double-spend scare. Team finally shares vocabulary on retries.
Nadia · Engineering manager · Fintech startup · 5/5
Short course — predicate section felt dense. Still worth it for the replayable notebooks.
Takeshi