Requirements

Functional Requirements:

• User send a long URL.
• System take that long URL
• and return a short URL which will work exactly the same
• user access that short URL and see the same behaviour.

Non-Functional Requirements:

• High Availability : The service must be always up so people can send their long URL and get a short URL.
• Low Latency : Retrieving the short URL must be instant.
• Durability : Once Long URL added, it shouldnt be lost.

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 /v1/shorten

Request : {"longUrl" : "https://longUrl", "alias" : "testLongUrl"}

Response: {"shortLink": "https://shortLink"}

• GET /v1/{shotURL}

Request: {"shortURL": "https://shortURL"}

Response: {"LongURL": "https://LongURL"}

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.