Problem context and objectives
Lead systems engineer · Seat Lock Bastion
Design the reservation path for event tickets when millions of users arrive at once and payment providers may time out.
The design must survive burst 2M users/min and inventory 50K seats. Every box must earn its place by satisfying a requirement or containing a failure.
How you win
- 1Trace one user action from request to durable outcome
- 2Connect every component to a stated requirement
- 3Explain the losing tradeoff, not only the chosen technology
Rules and pressure
- burst: 2M users/min
- inventory: 50K seats
- No overselling
- Expiring holds
New words in this mission
Open a term for a plain-language explanation.idempotent operation+
Repeating the same request has the same final effect as doing it once. This makes automatic retries safe.
Live architecture trace
Seat Lock Bastion: request to outcome
Buyers sends “enter” to Admission gate. Admission control protects the scarce reservation path and makes overload behavior intentional.
Design the reservation path for event tickets when millions of users arrive at once and payment providers may time out. Follow one real user action through the complete architecture; a component is useful only when you can explain the request, state, or failure it handles.