Loading...
generate short url: user provides a url, return a shorten url, short url is 1-1 mapping to original url
use short url to visit original url: user visit short url, it could be redirected to original url
high availability
quick response time for generating short url
could handle large traffic in short time
durability, could store 5-year url data
tiny url create: 200 / s, peak: 2000/s
tiny url read: 20k / s, peak: 200k / s
data retention: 5-year
storage:
each item: short url, original url, user id, created time
each item around 300 bytes
total size: 300 * 200 * 60 * 60 * 24 * 365 * 5 / 1024 / 1024 / 1024 = 8811 GB
Define what APIs are expected from the system...
GET /api/tiny_url/{shorten_url}
PUT /api/tiny_url/{shorten_url}
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...
redis + mysql
In mysql
shorten_url VARCHAR(8) primary id
original_url TEXT
time_created DATE
user_id VARCHAR(50)
In redis shorten_url is key, others are value
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?