Requirements

Functional Requirements:

• Create a short URL for a given long URL.
• Return the long URL associated with a given short URL.

Non-Functional Requirements:

• Estimate Queries per second ( QPS). Assume 1 million hits in day to convert to short url . This turns out to 1000000/3600*24 = 11 QPS .
• Calculate database storage requirements . Assume each record in takes 1 Kb . To calculate storage for 3 years : 1 Kb * 1000000 = 1 GB * 365 * 3 = 1095 GB i.e 1TB .
• System should be highly available .

API Design

Two major API's required :

1. url/convert : This URL will accept long URL , store to DB , return converted short URL .
2. url/retreive : This will receive short URL , search for corrresponding long URL and return redirection Http code in response .

High-Level Design

Describe the overall system architecture. Identify the main components needed to solve the problem end-to-end. Use the diagramming tool to create a block diagram.

Detailed Component Design

1. Conversing of Long to short URL can be done via Hashing Functions .

To save in database , 3 main columns , primary key ( ULID) , long URL and Short Url .