System requirements


Functional:

List functional requirements for the system (Ask interviewer if stuck)...

  1. give a city can return a list of cinemas in this city
  2. select a cinema, can get a list of shows in this cinema
  3. can book a show with seats


Non-Functional:

List non-functional requirements for the system...


  1. high available
  2. low latency


Capacity estimation

Estimate the scale of the system you are going to design...

DAU: 1 million




API design

Define what APIs are expected from the system...

searchMovie()

bookShow()



Database design

Defining the system data model early on will clarify how data will flow among different components of the system. Also you could draw an ER diagram using the diagramming tool to enhance your design...

Cinema table:

cinema id

city


cinemaHall table:

cinemaHall id

cinema id


cinemaSeat table:

cinema seat id

cinemaHall


movie table:

movie id

movie name

movie type


show table:

show id

cinemaHall id

movie id


show seat table:

show seat id

seat price


booking table:

booking id

show id





High-level design

You should identify enough components that are needed to solve the actual problem from end to end. Also remember to draw a block diagram using the diagramming tool to augment your design...

client: mobile, desktop, web

booking server: manage booking related

movie server: manage movie related

user server: manage user related, sign up, login





Request flows

Explain how the request flows from end to end in your high level design. Also you could draw a sequence diagram using the diagramming tool to enhance your explanation...


client send a search movie request, booking server returns a list of shows available

client send a booking request, booking server booked a list of seats selected



Detailed component design

Dig deeper into 2-3 components and explain in detail how they work. For example, how well does each component scale? Any relevant algorithm or data structure you like to use for a component? Also you could draw a diagram using the diagramming tool to enhance your design...

active booking service:

show id, [booking time, seats]







Trade offs/Tech choices

Explain any trade offs you have made and why you made certain tech choices...






Failure scenarios/bottlenecks

Try to discuss as many failure scenarios/bottlenecks as possible.






Future improvements

What are some future improvements you would make? How would you mitigate the failure scenario(s) you described above?