Loading...
List the key functional requirements for the system (Ask the AI for hints if stuck)...
database, server
List the key non-functional requirements (performance, scalability, reliability, etc.)...
load balancer, rate limire, cdn, cache
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...
There should be a shortening api and a redirecting api. the shortening api uses a hash function. the redirecting checks the longurl associated with the shortened api.
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.