Requirements

Non-Functional Requirements:

• API gateway
• Load Balancer
• Database
• Cache

Capacity Estimation

• ~500 million new URLs created per month — the write path
• ~100 million reads per second at peak — the read/redirect path

API Design

Two services, GET and POST

• POST /urls/short
  • Request body: { "longURL": "www.loooooongurlexmaple.com" }
  • Response: { "shortURL": "www.sh.com/zwswe" }
• GET /urls/translate/{shortURL}
  • 301 or 200

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

I this case i considere to use a relational database to store ui incremental, short url and long url

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.