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.)...
• API should be fast retrieval should be fast
• should be highly available
• Able to restrict too many request from single user

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 - api/vi/createURL { longUrl ,userId, timestamp , return short url}

get -> api/v1/getLongUrl{ short url, userId}

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.

Components will be user, write server , read server, database and cache for quering highly asked APIS

Write server - will have convert long to short url

1. we can apply a hashing technique to create a unique short url and at the same time
2. for hashing we will choose base62 cause it will have more combination of keys
3. Sharding as well based on user id

Read server - We can use redis for freq reads else we use Db calls

LRU cache in redis \

We will also have a load balance to ensure system is not overloaded

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.