Loading...
List functional requirements for the system (Ask the chat bot for hints if stuck.)...
1) Given a long URL generate a short url and persist it.
2) redirect short urls to actual URLs
List non-functional requirements for the system...
1) system should be fast, redirecting should be done in milliseconds.
2) generation should be done within seconds.
3) system should be highly available and consistent.
Estimate the scale of the system you are going to design...
10 requests each seconds for TinyURL Generation.
1000 for redirect.
each entry in db will take approximately 256 B (long url(100B), short(8B), user(50B),Expiry(50B))
so each day total storage required will be 10*60*60*24 Bytes.
Define what APIs are expected from the system...
1) generate(string originalURL) :- returns the generated TinyURL
2) redirect(short url): redirect to original 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...
Database will have below information for each URL
1) Original URL
2) Short URL
3) user
4) expiry
we can use noSql DB
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...
server : generate the url and maps the short url to original URL
cache: for faster mapping of URLs
DB: to persist the data and serve data incase cache misses
API gateway: all requests go through this, (DDOS protection and exponential backoff can be managed)
CDN: to serve user faster for redirect
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?