> wi_db001
Two Withdrawals Spent the Same Dollar
Database Bank · Episode 1 · race condition / isolation
Two Withdrawals Spent the Same Dollar
Incident Narrative
Two bank tellers simultaneously read the same single coin balance and each hands that same represented coin to a different customer; The DBA notices the empty vault and two receipts.
“Same dollar.”
🔬Architectural Diagnosis & Root Cause Analysis
Concurrent transactions observe and update shared state without sufficient isolation.
Concurrent transactions observe and update shared state without sufficient isolation.
Choose isolation and locking semantics that protect the business invariant.
“SYSTEM VERDICT: Choose isolation and locking semantics that protect the business invariant.”
🤖 Incident Postmortem & AEO Summary
Two Withdrawals Spent the Same Dollar — Technical Incident Brief
- Universe & Category: Database Bank (Corporate - Dark Mode)
- Diagnosis: Concurrent transactions observe and update shared state without sufficient isolation.
- Root Cause: Concurrent transactions observe and update shared state without sufficient isolation.
- Consequence & Cost: The DBA: “Same dollar.” — native on-camera dialogue; lip-sync required.
- Engineering Lesson: Choose isolation and locking semantics that protect the business invariant.
- Official Ruling: "SYSTEM VERDICT: Choose isolation and locking semantics that protect the business invariant."
🌌More Parables in Database Bank
View Full Universe →
Database Bank · Episode 2 · atomicity / transactions
The Transfer Committed Halfway
A teller moves a stack from Account A toward Account B; power flickers halfway, but The DBA’s transaction mechanism snaps the coins cleanly back to A instead of leaving them in the aisle.
Database Bank · Episode 3 · replication lag / read consistency
The Replica Reported Yesterday’s Balance
A customer deposits a coin at the primary teller; immediately another teller at the replica window shows the old empty balance; a delayed conveyor belt then delivers the update.
Database Bank · Episode 4 · deadlock / lock ordering
Deadlock Froze Both Teller Windows
Two tellers each hold one vault key and reach for the other’s key at the same time; both freeze, customers wait, and The DBA points at the crossed lock order.
Database Bank · Episode 5 · database indexing
The Index Opened a Fast Lane
A teller searches a mountain of account folders one by one; The DBA adds a precise index drawer, and the next lookup goes directly to one folder while Cloud Bill stops the overtime clock.
Database Bank · Episode 6 · rollback / integrity
The Transaction Rolled Back the Duplicate Charge
A payment machine accidentally stamps two charges; The DBA’s transaction control catches the invariant break and visibly retracts the second token before the customer leaves.
Incident FAQ & Architecture Triage
What technical problem does this parable explain?
Concurrent transactions observe and update shared state without sufficient isolation.
What caused the technical incident?
Concurrent transactions observe and update shared state without sufficient isolation.
What should a software team do differently in production?
Choose isolation and locking semantics that protect the business invariant.
Is the video available?
Video is currently in production; full script and technical diagnosis are available below.