Requirements

Functional Requirements:

• Create a short URL for a given long URL.
• Return the long URL associated with a given short URL.
• Shortened URLs should be between 6 to 10 characters long
• If long URL is resubmitted then use already generated short URL

Non-Functional Requirements:

• List the key non-functional requirements (eg low latency, scalability, reliability, etc.)...
• Scalability
  • Storing URLs, need to consider how long so we can decide what kind of DB storage solution
• How many users?
• How many requests?
  • Let's saw 10M requests a day
  • 10:1 Read:Write ratio
  • 100M Reads for every write
• Dealing with read heavy, since after a url is generated many users will be clicking on it

API Design

Define the APIs expected from the system. This is your chance to analyze and define the read and write paths so that you can come up with the high-level design...

POST /longUrl RESPONSE {id}

GET /shortUrl/{id} RESPONSE str

PATCH /longUrl/{id}

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.

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.