System requirements

Functional:

1. Create short url: system must allow user to input long
2. Redirect short

Non-Functional:

1. High availability: The system should be operational and accessible at all times.
2. Low redirect latency: The time taken to redirect from the short URL to the long URL should be minimal.
3. Horizontal scalability: The system must be able to handle increased load by adding more servers rather than upgrading existing ones.

API design

shortenUrl()

• Input: a long Url
• Output: A shortened Url.

redirectUrl()

• input: shortened Url
• Output: HTTP 302 Redirect to the original URL.

High-level design

The design is client will request to server for shortening the url, and for shorten url, it will save the url to database as key value format

When getting redirect url, for the first time request it will check the db and return 302 response, then put the visited data to redis cache, after that similar request will be provided by redis cache

Detailed component design

Shortener service will receive long url, and will generate short random string as shortened url, it will return to user as something like https://bit.ly/asHao9

After returning the short url, shortener service will input that to redis for faster access

Database design

Table: url

Column:

URL: Varchar(200)

ShortenedUrl: Varchar(20)