Loading...
List functional requirements for the system (Ask the chat bot for hints if stuck.)...
The system should shorten a long URL by generating a unique short URL and store the mapping in the database.
The system should redirect users to the original long URL when they access the corresponding short URL.
The system should generate a unique, collision-free key for each long URL to be used in the short URL.
The system should validate and ensure the correct format of the long URL before creating the short URL.
The system should handle and display appropriate error messages for invalid, non-existent, or expired short URLs.
List non-functional requirements for the system...
performance
scalability
reliability
security
maintainability
Estimate the scale of the system you are going to design...
Storage: ~1.3 GB for storing 10 million URLs.
Bandwidth: ~1 TB per year for handling 1 billion clicks.
CPU: At least 11.57 days of CPU time per year, assuming 1 ms per request.
Memory: ~124 MB for caching 10% of URLs, plus additional for operations.
Define what APIs are expected from the system...
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...
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...
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...
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...
Explain any trade offs you have made and why you made certain tech choices...
Try to discuss as many failure scenarios/bottlenecks as possible.
What are some future improvements you would make? How would you mitigate the failure scenario(s) you described above?