System requirements

Functional:

• Allow user to input a long URL
• Redirect the user to the long URL using the new shortened URL
• Allow the user to retrieve the original long URL using the short URL

Non-Functional:

• Scalability. Multiple users should be able to use the service concurrently.
• Security. Ensure that the new URL only leads to the original long URL
• Performance. Ensure the URL service generates the new URL efficiently.
• Reliability. The service should be available at all times.

Capacity estimation

The core functionality of the system is relatively simple, so the primary concern for capacity will be related to the scalability of the number of users. For a URL shortening service, we can assume an average of 500,000 requests per day.

API design

The APIs for this service will be as follows:

• URL encryption API: This will involve taking a long URL as input, creating a new short URL, saving the long URL and short URL to the database and returning the short URL.
• URL decryption API: Given as input a short URL, this API will retrieve the long URL associated with the short URL in the database and return the long URL to the user.

Database design

The database will contain a single table which we will call URL, where each row in this table, will have an id, a short URL, and the original long URL

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

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?