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

The client will click Submit/ enter the details including the url to shorten this will hit the backend code that is in our server which is the middleware..this will de-route it to the database store the long url, the code in the server will generate a short ur; store in DB and send back either by put response or via Webhook response bacl to the same user,So whenever user submits a request it submits to the server.

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.

Client->API->Cache memory(redis) check if information is already there -> if not go to server-> databse-> api response back

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.

Using Bit62Encoders for the server side logic and using cache upfront for faster lookup