Loading...
1.Need to generate shortened url for the given url
2.for given shortened URL need to retrieve original full URL and redirect to original url
3check id shortned url exist
1should be high available and fault tolerance
2should be low latency
3should be able to handle large amount of data
4should support growing number of user
1. approx 1 ml active user per month upto 1bl total user
2. Average 10 ml shortened request per month , peak may upto more than 1bn
3.Size of max long url support upto 500 byte with
Size of shorten url 8byte base 62 average, monthy database size
508byte * 10ml = 5gb
4.Clicks per shortened URL per month: 1000
5.Peak hourly traffic: 10% of monthly traffic (100,000 URLs shortened, 1 million clicks)
6 1 : 200 write /read ratioj , for 100 ml write read
20bl
7 Peak hourly 10% of monthly 2bl
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?