Loading...
List functional requirements for the system (Ask the chat bot for hints if stuck.)...
Need to build a web application
alphanumeric with 6-8 characters
assuming url's are stored for 1 year
each url size is 1KB
List non-functional requirements for the system...
Avoid collisions
scallable
Estimate the scale of the system you are going to design...
As the size of URL is 6 characters long, we can produce upto 62^6=5.6 billion unique urls.
writes 200rps assuming 1kb per write. So in total 200*1kb=200kb
in one day = 200*86400 = 17280000 17.2 GB / day
for 1 year 17.2*365 =6.27 TB / year as a bottle neck we consider 10TB/year
for reads, 20,000 rps
this means we need more reads capacity units than WCU's.
Since there is need for low latency and high scallability and since the reda requests are more we can use nosql database DynamoDB.
Define what APIs are expected from the system...
GenerateID
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?