Requirements

Functional Requirements:

• Create a short URL for a given long URL.
• Return the long URL associated with a given short URL.

Non-Functional Requirements:

• high availability, low latency and un-guessable Ids

API Design

• POST: api/vi/shorten
  • request :{"longUrl":"https://example.com/veryLong/path"}
  • response: {"shortUrl":"shortId"}
• GET: /shortId
  • Return: 301 redirect original url

High-Level Design

Write Path: User sends a long URL

-> Load Balancer -> App Server -> Gets unique ID from Counter Service ->Stores in DB -> Returns short link.

Read Path: User clicks short link -> Load Balancer -> App Server -> Checks Cache (Redis) -> If not found, checks DB ->Returns 301 (Permanent Redirect).

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.