Loading...
Assuming we get 5000 MAUs first month, each user may created up to 10 URLs. This means 50000 write operations the first month. If each URL gets accessed by average of 100 people (which is high), that's 5,000,000 read operations per month. Breaking this down, that's <1 TPS on the writes and 2 TPS on the reads. If we scale to 50000 MAUs by the end of the first year in production, we'll need to support 1 TPS on the writes and 20 TPS on the reads.
/url/shorten
/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...
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?