Loading...
Convert long URL to short URL -> Save mapping
Redirect short URL to long URL
Collision handling
Availability
Low-latency redirection
100k DAU -> 4k hourly -> 1 per second
1M converts per day -> 10 per user -> 10 generated URLs per second
30M seconds in a year -> 300M generated URLs in a year
6 bits to encode a character -> 30 bits in a new string
^probably dominated by 200 bytes of old URLs stored
60B bytes -> 60 Gigabytes yearly
POST /shorten/long_url
GET /redirect/short_url
long_url:string
short_url:string
date_created:datetime
cache
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?