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: The system should be designed to be highly available, ensuring that users can access the service at any time without interruptions.
• Low redirect latency: It's important to minimize latency during redirection to enhance user experience, making the service feel fast and responsive.
• Horizontal scalability: The system must be able to scale horizontally to accommodate high traffic volumes as the user base grows, ensuring consistent performance.

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...

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.