System requirements

Functional:

1. Shorten the URL
2. Maintain Record for 1 week for free users
3. Provide access for subscribed person who avail our subscriptions an all Shorterned URL will preserve for 1 month period max
4. Have option for renew that URL if its most Urgent and shared publicly

Non-Functional:

Availability, Super Fast and stored it in REDIS

Capacity estimation

System can handle 1 million request per seconds that covers creation and redirection requests.

API design

1. Shorten URL - publicly available
2. Redirect - publicly available
3. Login
4. Register
5. Subscribe
6. Profile
7. URL lists
8. Extend Expiry.

Database design

Users

Subscriptions

URLRedirections

High-level design

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

Try to discuss as many failure scenarios/bottlenecks as possible.

Future improvements

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