Ticket Master System Design

转载，经个人总结自https://www.hellointerview.com/learn/system-design/answer-keys/ticketmaster

functional request

1. User view tickets
2. User searches for available tickets
3. User books tickets

Non-functional request

1. User view& search needs availability, User book needs consistency
2. searching latency < 500ms(pretty low)
3. popular events handling
4. read heavy system

Core entities

1. Users
2. Events
3. player
4. Venue
5. Ticket
6. Booking

API Design

GET /view/event:eventId
-> Event & Ticket & Venue etc
知识点：GET请求一般是最好不要+request body
POST /search?eventId = {} & startTime={}&…
->Event & Ticket & Venue etc

POST /book/event {
eventId,
paymentInfo
} -> ticketId

Raw high level design

attention, for every service you need to explain the service flow.(User->api gateway->eventSVC->get Events)

deep dive high level design

主要用来解决non-functional requirement，深入讨论一下每一个我都需要一些什么东西