Loading...
List the key functional requirements for the system (Ask the AI for hints if stuck)...
Users should be able to park their car
Users should be able to retrieve their car after it's parked
Users should be able to pay for parking based on the duration
List the key non-functional requirements (performance, scalability, reliability, etc.)...
Consistency over availability - no giving the same parking spot to multiple people
Low latency, 500ms limit per transaction
Estimate the scale of the system. Consider daily active users, read/write ratio, storage requirements, bandwidth, and any relevant QPS calculations...
100M DAU across multiple regions
peak hours would have about 50M requests in a 2 hour window (8am - 10am) , (4pm - 6pm)
about 7000 queries per second at peak time
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...
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...
Deep dive into 2-3 key components. Explain how they work, how they scale, discuss tradeoffs, capacity, and any relevant algorithms or data structures.