System requirements

Functional:

1. The system should generate unique short URLs for long URLs
2. It should be fast
3. The short URL should take the user to the long URL
4. The short URLs should be invalidated after x number of years

Non-Functional:

1. The system should be consistent; the same URL should give the same output
2. The system should be scalable to address multiple users
3. 
   

Capacity estimation

50 million users per month, assuming 1 million writes and 10kb per write

1*10=10GB per month

120GB per year

API design

check_short_exsists(long_url)-> to prevent overwrites, returns none if empty else, the short string

create_short(long_url)-> creates short and returns the result

get_long(short_url)-> Given the short URL sends the long URL, enabling user to visit the page

generate_token(long_url) called by create_short API creates a short based on the hash

Database design

URL Table:

1)Primary Key (int)

2) Long URL (varchar)

3) Short URL (var char)

4) Created (DateTime)

5) Access times (int)

High-level 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...

Request flows

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...

Detailed component design

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...

Trade offs/Tech choices

Explain any trade offs you have made and why you made certain tech choices...

Failure scenarios/bottlenecks

Future improvements

What are some future improvements you would make? How would you mitigate the failure scenario(s) you described above?