Loading...
The URL provided by the user should be shortened and will be given back to user as response. The shortened URL will now redirects to the original long URL.
Performance: The service should have rate limitor and the throughput should be high. The latency should be low.
Lets suppose the number of average users per hour is 1000. Then in one day, the total visitors are 24000.
Therefore 24000 unique records will be generated.
Assuming that one URL takes up 10KB of space then per day the DB size requirement is 10*24000 KB= 240MB.
The surge policy will be 7 days , so in total we need DB of size 7*240 MB = 1680MB ~ 1.5GB of space.
Endpoint= /convertURL
Working => It will convert the long url to short url and persist in the DB.
Parameter=> Long 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...
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?