Requirements

Functional Requirements:

1. create shortern Code for original URL
2. redirect shortern url to original URL
3. Short URLs persist indefinitely

Non-Functional Requirements:

1. low latency for fetch url and redirect url
2. Availability > consistence
3. support to scale up to 100M URL creates per month and 1 billions redirect daily
4. Reliability -- at least one node response.

Capacity Estimation

100 000000 /(24 * 3600 * 30) = 38 URL creates per sec

100 0000000 / (24 * 3600 * 30) = 380 redirect per sec

Read Write Ratio 10:1

So assume 38 * 10 URL creates per second in peak traffic

3800 redirect per sec in peak traffic

API Design

POST /v1/api/create

request:{

original_url

}

response:{

statusCode

message

id

shortern_url

}

GET /v1/api/{shortern_url}

response:{

statusCode: 301/302/XXX

message

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