Loading...
The user gives us a URL, we return to the user a shorted URL using our domain. If the user clicks on the shorted URL, it should redirect them to the original URL they gave us
No conflicts between URLs we give out
100 million redirects would require 6 digits in the url
We would need to store 100 million records
shortenURL( String userUrl )
findURL( String tinyUrl )
deleteURL( String tinyUrl )
shortened_urls {
long shortened_url_id- primary key
String tinyUrl - unique
String userUrl
long user_id - foreign key
}
users {
long user_id - primary key
...
array shortened_url_ids
}
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?