How Not to Sell the Same Ticket to Two Different People
summary
An examination of why a ticketing app can sell the same cinema seat multiple times or oversell seats, despite a polished UI and deployment. It reviews real incidents and explains database-level causes and current database techniques (e.g., concurrency control, transactions, isolation levels, locking) that help prevent duplicate or oversold bookings.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 3:28Concurrency in ticket sales
- 10:11Problematic use cases
- 23:55Transaction solutions
- 33:07Non-transaction solutions
- 42:17Summary
- 45:13Q&A
related talks
41mCapacity and Stability Patterns
41mConcurrency, Scalability and Transactions -- Myths and Surprises
28mPractical Approaches To Scaling Distributed Transactions
42mStandby in Combat: Scaling an App in the World's No.2 Classifieds
32mThe Very Hungry Transaction
25mMultitenant applications: how and why
25mAvoiding Disaster: Practical Strategies for Error Handling Slides
02h 51mLet's Give DDD Back to Developers