Designing a Simple URL Shortening Service: A TinyURL Approach Submissions

Users can create a short URL.
Users can access the original URL using the short URL.
The system should be highly available and scalable.
URL redirects should have low latency.

10M daily active users
10 requests per user per day
≈ 100M requests per day
≈ 1,200 requests per second
Read-heavy workload

POST /shorten
GET /{shortCode}

URLMapping:

- id

- short_code

- original_url

- created_at

- expires_at

short_code should be unique and indexed.

Use a relational database such as PostgreSQL.

Short URL creation:

Generate a unique short code and store the URL mapping.

Redirect:

Look up the short code and return the original URL.

Caching:

Cache frequently accessed URLs to reduce database reads.

Scaling:

Scale application servers horizontally as traffic increases.