Loading...
Allow users to park, allocate them a parking space according to vehicle and accessibility tag.
Authenticate the users if they have a parking card
Charge the Users to their card, or using a payment processor, according to the time spent in the parking
Storing the Parking Data in a data Structure like HashMap, or a database
Consistent, No Collisions
Low Latency
Estimate the scale of the system you are going to design...
/allocate (CarType, User) returns a unique parkingId, parkingSlot
/checkout (User)
UserTable with list of Users, with their Car Types, Status like if they require accessibilty needs
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...
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...
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...
Explain any trade offs you have made and why you made certain tech choices...
Try to discuss as many failure scenarios/bottlenecks as possible.
What are some future improvements you would make? How would you mitigate the failure scenario(s) you described above?