Loading...
List functional requirements for the system (Ask the chat bot for hints if stuck.)...
Create URL
List non-functional requirements for the system...
Bandwidth:
Lets estimate 400M users per day, 80/20 read heavy url. Each url is 128 bytes with 256bytes meta data. 80M Write per day so 32Gb/day=0.37 bytes / second write for bandwidth, 320M Read per day 128GB read.
Storage:
Storage is per day, with log of a year, replicated for additional redundancy, high availability and backups.: with a factor of 3
shortenURL(str long_url, user_ID, expiration_time=None): Takes a long URL and returns a short URL.
redirectURL(str short_url): Takes a long URL and returns the associated long URL.
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...
what should i do here?
Explain any trade offs you have made and why you made certain tech choices...
Explain
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?