Design Ticketmaster
Sell tickets to concerts and games, with seat maps and huge rushes when popular events go on sale.
Functional requirements
- Browse and search events
- Pick seats and hold them while paying
- Buy tickets and get a confirmation
Non-functional requirements
- A seat is never sold twice
- Stays up when millions join an on-sale
- Search results in under 500 ms
Scale
- 100K events, 10M tickets sold per month
- A big on-sale draws 10M users in minutes
- Browsing outnumbers buying 100 to 1
How you’ll be scored
9 checks covering your diagram and your notes, and any valid approach counts. Hints appear for anything you miss. Common mistakes, such as single points of failure or components you never explain, cost points. How grading works
What interviewers look for
- Clarify before you draw. State what is in and out of scope. For “Design Ticketmaster”, that starts with: Browse and search events; Pick seats and hold them while paying; Buy tickets and get a confirmation. Interviewers notice candidates who pin the requirements down first.
- Turn the scale into numbers. The scale (100K events, 10M tickets sold per month; A big on-sale draws 10M users in minutes; Browsing outnumbers buying 100 to 1) should become requests per second, storage and bandwidth, and those figures should drive your choices. Estimates with units carry more weight than adjectives.
- Show how each quality is met. Your design should visibly deliver: A seat is never sold twice; Stays up when millions join an on-sale; Search results in under 500 ms. Saying that it does isn’t enough; point to the part of the design that makes it true.
- Expect follow-ups on the hard parts. Interviewers usually probe reservations, consistency and spikes here. This is a medium problem, so interviewers expect you to weigh two reasonable options, such as consistency against latency, and to say why you picked one.
- Explain failure and trade-offs. Say what happens when a component fails, where a single point of failure would hurt, and what you chose not to build. Naming a trade-off is a stronger answer than claiming there isn’t one.