ORIGINAL SYSTEM DESIGN QUESTION
Timed ticket reservations
Sell limited seats with temporary holds, payments and cancellation.
Original exercise · advanced. Editorial role relevance does not imply a company has asked this question.
Requirements and constraints
- 20,000 buyers arrive in one minute for 5,000 seats.
- No seat may be sold twice; payment callbacks may retry.
- State assumptions and justify security, cost, operational ownership and data retention.
Pressure round
Payment succeeds seconds after the seat hold expires.
Build and explain the design
Requirements & scope
Who uses it? What must it do? What is explicitly out of scope? State latency, durability and privacy goals.
Self-review guidance
Define the actors, required operations and out-of-scope behavior. Explicit requirement: No seat may be sold twice; payment callbacks may retry.
Capacity estimates
State assumptions, peak requests/second, data volume and retention. Show your arithmetic and units.
Self-review guidance
Use this workload: 20,000 buyers arrive in one minute for 5,000 seats. Convert rates and payload sizes into peak compute/storage assumptions; show units, headroom and what remains unmeasured.
APIs & data model
Describe endpoints/events, entity keys, indexes, authorization, and idempotency.
Self-review guidance
Define hold IDs, expiry semantics, seat ownership and payment idempotency.
Architecture & data flow
Describe components and request/event paths. Use plain text arrows to sketch your design; explain each responsibility.
Self-review guidance
Specify the transactional reservation authority, expiry worker and payment saga.
Failures & observability
What happens on overload, duplicate events, partial failures or lost dependencies? Discuss monitoring and recovery.
Self-review guidance
Pressure-test: Payment succeeds seconds after the seat hold expires. Describe bounded recovery, deduplication, observability and a user-visible failure state.
Tradeoffs & alternatives
Compare two plausible approaches. State the costs, consistency model and what would make you change the design.
Self-review guidance
Choose compensation and reconciliation behavior rather than claiming cross-service atomicity.
Design guidance describes assumptions and tradeoffs; no architecture has been simulated or benchmarked.
Practice this question
Save your work privately, explain decisions and return to your revision queue.
Open practice workspaceBrowse the question library →