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.)...
• How short shoud a short url be?
• How many urls do we espect?

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 a long url, send back a reponse with a short url

Get short url, send back a long url

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.

So we have a client that send a long url as a post and we send back a sohrt one, and also it can send a short url as a get and we send back the long one.We have a server side app that comunicate and store in the db

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.

We have like 2 main component like short url and long url

and we need kind of hasing mecanism so when we recive an long url we can encode thme and garantie that its unic like a random genrator+a time stamp