Loading...
List functional requirements for the system (Ask the chat bot for hints if stuck.)...
Should support all the different vehicles
List non-functional requirements for the system...
Highly scalable and available
Fault tolorent
low latency
Estimate the scale of the system you are going to design...
As there are 3800 users and each user can at most make 12 requests in a day
so number of request in a day 3800*12 45600/86400 approx 1
Define what APIs are expected from the system...
/Reserve-paking it is used to reserve a parking return code 200
/clear-parking it is used to clear a parking spot
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...
As the system is write heavy we will use is write heavy so non relational database will be good
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...
user make a request to api server as the qps is very low so single node should be sufficient the api server chechks whether there is an empty spot if there is an emty then reserve the parking spot or it will return space not found
in order to clear the parking space the user request is directly forwarded to api server
that removes the entry from db
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...
user make a request to api server as the qps is very low so single node should be sufficient the api server chechks whether there is an empty spot if there is an emty then reserve the parking spot or it will return space not found
in order to clear the parking space the user request is directly forwarded to api server
that removes the entry from db
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...
For non relational database we can use Cassandra
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?