Loading...
The system should take a URL from the user and return a shortened URL. It should also on clicking of the shortened URL fetch the original URL. Can be done in a POST/GET manner as in Postman.
The Nonfunctional System requirements would include a high availability of the system.
The system should also have low latency and should be able to scale a large amount of data.
It should also be available over the world.
Fast redirection. Security considerations.
URL Creations: 100 reads per second.
URL Redirections: 10,000 per second.
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?