Capacity Planning
Design Ticketmaster · Part 5
Problem context
Design a system that sells tickets to events with assigned seats: users browse what's available, pick a seat, and buy it. The same seat must never sell twice.
In scope: browsing seat availability, holding a seat during checkout, purchasing a held seat, and releasing an expired or abandoned hold. Out of scope: dynamic pricing, seat recommendations, and the internals of the payment provider itself.
What a strong answer sounds like
State the decision, connect it to a requirement, and name the tradeoff. Keep the design focused on the workload in the prompt.
Ready for the capacity planning interview?
The AI interviewer asks about this part of Design Ticketmaster. The interviewer guides you through topics one by one.