Requirements

Functional Requirements:

1. Add a new URL (like https://www.youtube.com/) and generate a short alias for it
2. When requesting alias, redirect to the URL

Non-Functional Requirements:

1. Adding new url should be below 200 ms at p99
2. Redirecting should be below 50 ms at p99

Capacity Estimation

Daily users: 1 million / day

Storage capacity: 1 url = 50 bytes average

1000 new urls a day = 50kb per day, 1.5 mb per month, lets say 100 mb per 5 years shall suffice

API Design

POST /alias [URL] -> {url: "http://url123", alias: "abcd"}

GET /alias/abcd -> {url: "http://url123", alias: "abcd"}

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.

Database Design

SQL will be a good solution because our data is a relation by nature (relates URL and its alias), very natural

table alias{

url: varchar

alias: varchar

}

Detailed Component Design

No need for microservice architecture

1 monolith application is enough: 2 REST urls