Loading...
Generate unique short urls - Using encoding methods. 1. Pre-populate the short urls and assign a unused url for every new request. 2. Handle the short url as a base62 counter. Every time a new request comes increment the counter and assign the new unique url.
Redirect short url to original url
Check if url exist in db
API for url management
User authentication
Scalable - Horizontal (Can use a NoSQL DB like MongoDB which has a single leader architecture which means there won't be any write conflicts and read latency will be low.)
High availability using Replication
Assuming 100K users per day and 3 links per user
Each url is 500 bytes
Each unique url is of size 7
Total space per day = 500 bytes * 300000 = 150 MB
Number of unique URLs = 62^7
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?