System requirements

Functional:

• The short URLs doesn't have to be in structured format
• Shorts URL can be expired after a specific time stamp

Non-Functional:

• The system should process and generate short URLs within 200 milliseconds.
• The redirection from a short URL to the original URL should occur within 100 milliseconds.
•  99.9% uptime

Capacity estimation

• 10 million total URLs.
• 500k active URLs

API design

• GET /shorten-urls?url={originalUrl}
• GET /{shorten-url}/

Database design

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

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

We will using Load Balancer to allow horizontal scaling for proxy server. Url should be hashed to get the shorten one. We could use Redis as cache to get the original URL fast. We should pushing analytics event instead of asynchronous request to loosely couple analytics system with this one.

Trade offs/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?