Loading...
Given the original URL, convert it into short URL
Click on the short URL, it should redirect to the original URL
High availability
Strong consistency
10 Million DAU
10 Million URL -> 100 characters original URL -> 100*10^7 bytes=10^9 bytes = 1 GB of original URL
10 Million shortURL -> 40 characters long URL -> 40*10^7 = 0.4 GB of shortURL
write: reads = 10 million : 10*10 million = 1: 10
read-heavy system
- Detection Service for short vs original
- Shorten service can first check if that original URL is already present in the data store then return that shortURL,
else generate a shortURL for the given originalURL
- FetchOriginalURL throws an exception if shortURL is not present in the datastore
Objects:
URL
- short URL | 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?