Loading...
The system would be able to:
The system would be optimized for space???
No double booking for same spot.
Reserved spots shouldnt be allocated for daily users.
Reserved spots would be given a id which needs to shown at entrance time.
Different rates for booking and daily entries.
Booking rush hour - no double booking
Daily rush hour - shud be fast to allocate spots and be accurate too without double allocating.
Estimate the scale of the system. Consider daily active users, read/write ratio, storage requirements, bandwidth, and any relevant QPS calculations...
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...
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.
which type of db? - sql.
Deep dive into 2-3 key components. Explain how they work, how they scale, discuss tradeoffs, capacity, and any relevant algorithms or data structures.