Loading...
List the key functional requirements for the system (Ask the AI for hints if stuck)...
1) url shortning
List the key non-functional requirements (performance, scalability, reliability, etc.)...
1)easy to use
2)fast
Estimate the scale of the system. Consider daily active users, read/write ratio, storage requirements, bandwidth, and any relevant QPS calculations...
daily active user- 1million
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...
1)user input for url shortning
2)serach
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.
1)user input
2)data storage
3)short url gentrator
4)search logic
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...
us
Deep dive into 2-3 key components. Explain how they work, how they scale, discuss tradeoffs, capacity, and any relevant algorithms or data structures.