Loading...
1) we should be able to generate URLs for every request
2) Users should be redirected to the actual URLs
3) There should be an expiry for every url
1) High Availablity
2) Eventual Consistency
3) High Reliability
4) Fault Tolerant
DAU: 10 million users
Total Daily URL shortening requests: 100 million
Read/Write Ratio: 100:1
Bandwidth:
Write Bandwith: 1 Url will have metadata with details such as id,URL,expiry_time, expected size: 100bytes
Write Bandwidth: 100million*100bytes/day = 120kb/sec
Read bandwidth: 120kb/sec * 100 = 12MB/sec
Storage:
1 day storage = 100bytes * 100 million = 10GB
5 year to days = 365*5 ~= 2000
5 year storage = 2000 * 10GB = 10TB
Define what APIs are expected from the system...
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...
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?