Design a Ticket Booking System

1. Problem Statement

2. Architecture Discussion Map

Use this as one discussion aid, not a single correct answer. Your design should follow from the requirements, scale, and trade-offs you establish.

graph LR
    A["Design a Ticket Booking System"]
    A --> F1["Handling massive traffic spikes 1M+ concurrent users"]
    A --> F2["Preventing overselling Inventory Management"]
    A --> F3["Database Locking strategies Optimistic vs Pessimistic"]
    A --> F4["Virtual Queue / Waiting Room implementation"]
    A --> F5["Data Consistency ACID"]

3. Key Focus Areas

• 1
  Handling massive traffic spikes (1M+ concurrent users)
• 2
  Preventing overselling (Inventory Management)
• 3
  Database Locking strategies (Optimistic vs Pessimistic)
• 4
  Virtual Queue / Waiting Room implementation
• 5
  Data Consistency (ACID)

4. What the Interviewer Looks For

The interviewer probes these areas, and the report grades the interview against them.

• Requirements and capacity
• Inventory correctness and holds
• Admission control and traffic shaping
• Checkout and payment integration
• Resilience and read-path availability