Requirements

Functional Requirements:

1. Create a URL shortening service
2. ~10M new short URLs per day (about 115 writes/sec)
3. ~1B redirects per day (roughly 100:1 read-to-write ratio — typical for this type of service)(That's about 11,500 reads/sec on average)

Non-Functional Requirements:

1. Faster redirect under 200ms.
2. System should be up for 24x7

Capacity Estimation

Storage estimates:

• Each URL entry (short key + long URL + metadata) ≈ 500 bytes
• 10M new URLs/day × 365 days × 500 bytes ≈ 1.8 TB/year

API Design

Create URL:

POST: /short-url

body: {"url": "https://example.com/rugur/ufuf"}

Return: {"shortUrl" : "https://short.io/YdhTbd"}

URL Read:

GET: /get-url/YdhTbd

Return the url: https://example.com/rugur/ufuf

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.