# Design a Ticket Booking Site Like Ticketmaster

DevFeed: [Design a Ticket Booking Site Like Ticketmaster](<https://devfeed.tech/articles/design-a-ticket-booking-site-like-ticketmaster-32311.md>)

Original publisher: [Read original article](<https://evanking1.medium.com/design-a-ticket-booking-site-like-ticketmaster-d08b0f1bbb14?source=rss-9736778727ef------2>)

Author: Evan King

Published: 2024-11-27T05:34:17Z

Content type: tutorial

Language: en

Sources: [Evan King](<https://devfeed.tech/sources/evan-king.md>)

Topics: [Requirements](<https://devfeed.tech/topics/requirements.md>), [Availability](<https://devfeed.tech/topics/availability.md>), [consistency](<https://devfeed.tech/topics/consistency.md>), [Latency](<https://devfeed.tech/topics/latency.md>), [Low Latency](<https://devfeed.tech/topics/low-latency.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [availability](<https://devfeed.tech/tags/availability.md>), [booking](<https://devfeed.tech/tags/booking.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [latency](<https://devfeed.tech/tags/latency.md>), [low-latency](<https://devfeed.tech/tags/low-latency.md>), [requirements](<https://devfeed.tech/tags/requirements.md>), [strategy](<https://devfeed.tech/tags/strategy.md>)

## AI overview

A system-design tutorial for a Ticketmaster-like ticket booking site. It defines functional requirements for viewing, searching, and booking events, then outlines non-functional requirements including availability, consistency to prevent double booking, scalability, low-latency search, and high read throughput.

## Source excerpt

With Ex-Meta Staff Engineer & co-founder of hellointerview.comUnderstanding the Problem🎟 What is Ticketmaster? Ticketmaster is an online platform that allows users to purchase tickets for concerts, sports events, theater, and other live entertainment.Functional Requirements Core Requirements Users should be able to view events Users should be able to search for events Users should be able to book tickets to events Below the line (out of scope): Users should be able to view their booked events Admins or event coordinators should be able to add events Popular events should have dynamic pricing Non-Functional Requirements Core Requirements The system should prioritize availability for searching & viewing events, but should prioritize consistency for booking events (no double booking) The system should be scalable and able to handle high throughput in the form of popular events (10 million users, one event) The system should have low latency search (< 500ms) The system is read heavy, and thus needs to be able to support high read throughput (100:1) Below the line (out of scope): The system should protect user data and adhere to GDPR The system should be fault tolerant The system should provide secure transactions for purchases The system should be well tested and easy to deploy (CI/CD pipelines) The system should have regular backups Here is how the requirements might look on the whiteboard: Adding features that are out of scope is a "nice to have". It shows product thinking and gives your interviewer a chance to help you reprioritize based on what they want to see in the interview. That said, it's very much a nice to have. If additional features are not coming to you quickly, don't waste your time and move on.Planning the Approach Before you move on to designing the system, it's important to start by taking a moment to plan your strategy. Fortunately, for these common user-facing product-style questions, the plan should be straightforward: build your design up sequent