System requirements
Functional:
- Entry ticketing
- Exit ticketing with payment based on hours parked
- Login
- Search by venue
- Determine free slots
- Reserve slots
- Payment processing
- View/modify reservation
- View per user history
Non-Functional:
Performance: Quickly identify free slot as soon as vehicle exits lot. Low latency < 2ms for server to respond
Availability : Ensure uptime so that service is available at all times
Security: Authentication.
Capacity estimation
1M total users
100K active daily users
10K concurrent users
API design
REST API
- Login: POST v1/login
- View Location: GET v1/search?location=<location>&date=<date>&timerange=<timerange>
- Reserve slot: POST v1/reserve?location=<location>&date=<date>&timerange=<timerange> returns reservationid
- Cancel slot: POST v1/cancel?reservationid=<reservationid>
- Payment: POST v1/payment?reservationid=<reservationid>
- View history: GET v1/history?userid=<userid>
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...
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. If you are unfamiliar with the tool, you can simply describe your design to the chat bot and ask it to generate a starter diagram for you to modify...
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...
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...
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?