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:

• when requesting the long url from short url the P95 of response is within 100msec
• the availability should be more important than consistency
• when user creates the URl the replication to all destinations can be eventual

Capacity Estimation

The request for the url should be seved within 100msec

The creation of the url can be slower if needed

there will be 100m requests a day to get a query

there will be 1m requests a day to create / update / delete the questy

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.

Database Design

Define the data model. Identify the main entities, their attributes, and relationships. Consider the choice of database type (SQL vs NoSQL) and justify your decision based on access patterns...

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.