Requirements


Functional Requirements:


  • Users can see available events
  • Users can search for events
  • Users can book tickets



Non-Functional Requirements:


  • high consistency on ticket booking (no double-booking)
  • availability > consistency for new events
  • low latency on event search
  • scale to 10M DAU
Okay now I think I finished my my functional and non-functional requirements! Okay now I think I've finished my functional non-functional requirements!


API Design

Define the APIs expected from the system. This is your chance to analyze and define the read and write paths so that you can come up with the high-level design...




High-Level Design

Describe the overall system architecture. Identify the main components needed to solve the problem end-to-end. Use the diagramming tool to create a block diagram.





Detailed Component Design

Deep dive into 2-3 key components. Explain how they work, how they scale, discuss tradeoffs, capacity, and any relevant algorithms or data structures.