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:

List the key non-functional requirements (eg low latency, scalability, reliability, etc.)...

Capacity Estimation

Estimate the scale of the system. Consider daily active users, read/write ratio, storage requirements, bandwidth, and any relevant QPS calculations...

API Design

Going with RESTful API

POST: /create-url

GET :{short-url}

High-Level Design

First we have the client who will make an request to the Loadbalancer and Server will receive the Request which will use the base (62) mechanism to short the url and we have to store the long an d short url in DB so we can redirect the user to the long url using short url

Database Design

Datamodel Schema:

long-url:string

short-url:string

create_At:string

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.