Requirements

Functional Requirements:

1. User writes a long url and gets short
2. Short url redirects to long one
3. Short url lives one year

Non-Functional Requirements:

1. 1m users per day
2. 10 write requests per user a day
3. 1 thousand read requests a day
4. High availibility

Capacity Estimation

URL model:

{

int UrlId,

string ShortUrl,

string LongUrl

}

RPS write = 10^6 * 10 / 10^5 = 100

RPS read = 1000

1 link = 3kb

BD grow a day = 3kb * 10^6 * 10 = 3gb/day

BD grow a year = 3gb * 365 = 10^3 gb

API Design

URLs

GET api/user/{userId}/urls/{urlId}

POST api/user/{userId}/urls {url}

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

Define the data model. Identify the main entities, their attributes, and relationships. Consider the choice of database type (SQL vs NoSQL) and justify your decision based on access patterns...

Detailed Component Design

Deep dive into 2-3 key components. Explain how they work, how they scale, discuss tradeoffs, capacity, and any relevant algorithms or data structures.