Loading...
1.User giving long url, we need return uniq shortened url.
2.User giving shortened url, we need redirect to long url
Strong Consistency, high availability.
100,000 Daily Active Users (DAU).
During peak hours, we can estimate around 10,000 requests per minute.
QPS = 10000/ 60 = 1600
Read/write = 100/ 1
so very heavy read, write almost 16/ second
per day 100000/100 = 1000write times
assume each write 1KB, so every day add
1MB data, each year 400MB.
Define what APIs are expected from the system...
1. post: v1/shortenUrl/apikey
body{
long url: "www.ewbfiwbq.com/45325cvsuvfuqfqwefqefq"
}
response{
status: 200,
shortUrl: "r34r3ff_"
}
2.get: v1/getshortenedurl/apikey/shorturl=r34r3ff_
response:{
status: 200,
long_url: "www.ewbfiwbq.com/45325cvsuvfuqfqwefqefq"
}
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?