System requirements
Functional:
List functional requirements for the system (Ask the chat bot for hints if stuck.)...
Ability to reserve parking spot in advance.
Payment with mobile app integration
See if parking row has free spots
send invoices after payment
financial record keeping
User registration is needed
Can do "drive-up parking" and pay on the spot
10% of spots are for ev with charging station
differrent pricing for car types
Non-Functional:
List non-functional requirements for the system...
Should always be able to pay
Should save the video footage for at least 6 months
durability
Capacity estimation
Estimate the scale of the system you are going to design...
This system will be used by a lot of parking lots.
Most of the client will leave after 2hours when movie ends so not a lot of events
about 200 parking spots per parking lot
API design
Define what APIs are expected from the system...
Rest api. Main entities are user, spot, car.
So endpoints:
/users/signup
/users/authenticate
POST /lots/{id}/spots/{id}/reservation - reserve the spot
POST /lots/{id}/spots/{id}/pay - pay for the reservation
PATCH /lots/{id}/spots/{id}/reservation - update the reservation
GET /lots/{id} - return available spots and price
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...
User database - sql database to store user id , user info and hashed password
Payment database - store payments. Also Store payment records for 6 months
Blob for video footage storing
Parking lot db - store all the reservation and current info for each parking spot - price, type
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...
Client will first go throught CDN so it's faster for him to get cached data. Then will talk to api gateway and web app. For signup and auth request will go to users service which will store users info and will create sessions.
Payment service will handle all payment related stuff and save the info the db for storage. Payment service will also talk to third party systems.
Parking lot service will handle reservations and parking availability.
Blob storages stores video footage of the parking lot
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...
user can signup and authenticate
user can search for parking lot availability
user can reserve parking lot
user can pay for parking lot
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?