Loading...
Requirements:
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...
Storage:
URL is around 100 characters, 200 bytes
1 million URLs in database
200 million bytes or 200 MB of storage
Bandwidth:
10,000 users per day
10 urls to shortened
60% shorten URLs
40% redirected URLs
10,000 * 10 = 100,000 requests per day
100,000 / (70,000) = 1.4 requests/second
Define what APIs are expected from the system...
GET shortened URL:
parameter: given URL
return: shortened URL (string)
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...
key-valued stored database
{
id: unique value
metadata: string
timestamp: string
}
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?