System requirements

Functional:

Vehicle entry

Vehicle exit

Parking

Only one vehicle can enter at a time.

A reservation system to check for available spaces and show where these are.

Different spots for different vehicles like cars, motorcycles etc.

UI component so that users can see empty spots etc. either from web or mobile.

Non-Functional:

Availability through load balancing, failover mechanisms and redundancy.

Scalability on increased load using cloud solutions and microservices.

Security for preventing car theft through cameras and alarms

Usability

Capacity estimation

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

API design

Define what APIs are expected from the system...

Reservation API: Create, update, get, delete a reservation

Notification API: Create, update, get, delete a reservation

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...

Reservations Table

Columns:

Id, Car plate, Spot, Time in, Time out, User id (FK from Users Table)

Users table:

Columns:

Id, First Name, Last Name, Car plate

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...

Microservices: Reservation for reservations, Notification to handle notifications when spots become empty

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?