Loading...
This will be a SaaS solutioin and clients should be able to ingest their files with parking lots into the system.
Additionally there will be a UI to manage parking lots configuration from browser.
Each lot will have a set fields that will be configuring its behavior - for example disabled space, or space for trucks.
UI also will support manual plate endtry and lot allocation.
One more UI will be implemented for car users - they will be able able to look up their parking lot and time left by plate number.
It's possible to use dynamo db for parking lot table
Parking lot tablle should have current plate column and index based on current plate column
Estimate the scale of the system you are going to design...
Define what APIs are expected from the system...
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...
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?