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 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...

You would need apis to store the short url and long url

you would need basic secure apis for verification and user functionality

you would need apis to return the short 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.

We would have a backend relational DB like SQL server used to store our short urls, long urls, their relationship/mapping, and basic verification - APIs would be used when saving from UI, calling data from UI, and for user functionality - They would return the data to the UI

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 would have multiple servers scaled vertically to mitigate and bottlenecks, we would use a reverse proxy as a load balancer to direct traffic, this ensure reliability and redudancy for our system