Loading...
- User should be able to put a link and get a shortened link
-User should be able to use the shortened link and be redirected to the original website.
Let's say we have 10 million users. Every user will shorted 5 urls a day. So that is 50 million write/ day => (50, 000, 000)/(100, 000) = 500 writes per second.
For the reads (retrieving the long link). Assume that each user uses 50 urls of our shortened ones a day. So that is (50 query/day)*(10, 000, 000) = 500, 000, 000 reads/day
=> (500, 000, 000)/(100, 000) = 5000 reads/second.
POST /url
Body{
"long_url" : "https://something.com"
}
=> https://shorturl.com/abcdef
GET https://shorturl.com/abcdef
=> HTTP redirect request to original url
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?