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:

• low latency when redirecting
• availability and sacalability

API Design

There can be an API that takes in the original URL and substring the URL. The api should maintain unique urls these can be stored in a database once they are generated.

There can also be an get put and delete api on the specify url by the eligible user so they can modify or delete it.

Store the frequently being accessed api in a cache to avoid latency

High-Level Design

the design should include a client , server, Cache , Database , Load balancers for balancing the load.

should invole caching to avoid frequent db lookups when the traffic to a particular url is high.

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.