Loading...
List functional requirements for the system (Ask the chat bot for hints if stuck.)...
creating a new shortened url from a long url
redirecting users from shorenend url to long url
number of clicks
List non-functional requirements for the system...
Server should be up for all the time
url should redirect in 1 to 2 ms for seamless approach
scalablity: the system should be scalable
security: url should be stored securely.
Estimate the scale of the system you are going to design...
db should store around 10^9 short url
how many request will come at a time. Let say we can expect more than 10000 requests
cache should be fast
Define what APIs are expected from the system...
createUrl(Originalurl) -> shortUrl
getrul(shorturl) -> shorturl -redirect-> original url (302 permanently moved)
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?