Requirements
Functional Requirements:
- Users can see available shows.
- Users can view a seating map to pick seats.
- Users can book a seat to a show
Non-Functional Requirements:
- Low latency reads <100ms when viewing shows
- Booking seats should be strongly consistent otherwise prioritize availibility
- System should be scaleable and handle high traffic
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...
- GET /shows/:showId Return Show
- GET /shows/:showID/seats Return []seats
- POST /booking/:seatId Return T/F
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.