Loading...
the system converts long url to short url.
given a short url, the system redirect user to the long url.
the system should be highly avaiable (99.99% up time), highly reliable (no data loss), highly performant (response time under 100ms).
the system should prevent malicious request, allow user to customize the short url.
for write operation, the traffic is 100 million urls are generated per day. So it is 10^8/3600/24 = 1157 url/second. And read operation is 10 times of write operation, so read traffic is 1157*10 = 11570 url/second.
if we save the url for 10 years, and each url is 100 bytes, so total storage is 100million * 365days * 10years * 10bytes = 3.65*10^13bytes = 36.5TB
given a long url to get a short url: POST /api/v1/url/shorten, request parameter: long url (string)
return: JSON data include original url, generated short url, generated time, expiration time.
given a short url to access long url: GET /api/v1/expand?short_url={short_url},
where short_url is the short url user inputs for redirection.
return: a long url (string) for http redirect
HTTP status code:
500 SERVER ERROR
400 BAD REQEUST
404 NOT FOUND
200 SUCCESS
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?