Loading...
List functional requirements for the system (Ask the chat bot for hints if stuck.)...
Estimate the scale of the system you are going to design...
lets say we get x amount req per second, and we need to store them for 10years, our tiny url should be of size(n) and we include [A to Z] [a to z] and [0 to 9] char in url
y = x*60*60*24*365*10
n > celing ( logy/log62)
so if we get 400 req per second to create tiny url
y = 400 *60*60*24*365*10 = 126144000000
doing logy/log62 we get 6.1 , so we choose 7 as our tiny url size
Define what APIs are expected from the system...
POST /api/createtinyurl
GET /api/getFullURL/{tinuURL}
we will use cassedra as with data voulme as big as 126144000000 , my sql or RDBS might choke .
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?