Loading...
1000 request per second
32M second in 1 year
32G request in 1 year
320G request in 10 year
Short URL: 8bytes
LongURL: 400Bytes
Approx: 1kb for 1 URL
320G request * 1kb per request = 320TB
Define what APIs are expected from the system...
URL: /create_short_url
Method: Post
Response: 200
URL: /getURL
Method: Get
Response: 302
MappingID
urlmappingid:
ShortURL:
longURL
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?