Loading...
List the key functional requirements for the system (Ask the AI for hints if stuck)...
parking spaces like if there are 100 spaces then we have to fill them efficiently for both two wheeler and four wheeler parking
List the key non-functional requirements (performance, scalability, reliability, etc.)...
as many vehicles come, we have to fill them efficiently to the parking lot and also scale the lot if the available spaces are all filled and new vehicle comes in
Estimate the scale of the system. Consider daily active users, read/write ratio, storage requirements, bandwidth, and any relevant QPS calculations...
Define the APIs expected from the system. This is your chance to analyze and define the read and write paths so that you can come up with the high-level design...
GET next_parking_space => int => 200
POST fill_parking_space => 201
POST create_parking_space => 201
Describe the overall system architecture. Identify the main components needed to solve the problem end-to-end. Use the diagramming tool to create a block diagram.
Define the data model. Identify the main entities, their attributes, and relationships. Consider the choice of database type (SQL vs NoSQL) and justify your decision based on access patterns...
Model - parking lot
parking_space_id (int)
parking_type (int) - 2 wheeler/ 4 wheeler
filled (boolean) -true/false => default is false when its created
parking_number (int)
Deep dive into 2-3 key components. Explain how they work, how they scale, discuss tradeoffs, capacity, and any relevant algorithms or data structures.