Loading...
the user gives a url and system should generate a short url.
given a short url the system should redirect the user to the original long url.
the user should be able use custom short links. hard part: concurrency.
we should be able to count the number of times a link has been clicked.
expire a link after a time.
only a auth user shouldbe able to geenrate a url.
and we also want to make limit the size of the long url and also place rate liminting
generate url in 200 ms - sycrhnoous call.
redirect in 100 ms. p99 of 150 ms.
expirae the link in 30 days to a year or 2 year.
conflict resoultion
writes 500 writes per second
reads. 10k reeads per second. 10:1 read vs wrote or 100:1
Estimate the scale of the system you are going to design...
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?