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

High-Level Design

I have a redirecting service hosted at www.shorten-url.com. To create a short url, I'll generate a unique id w low-collision for the url provided and store it in a hash table. When my service is hit with www.shorten-url.com/, ill retrieve long url from hash-table and redirect to it.

Scaling my service would be through horizontal scaling of web service and hash table as a separate backend service with APIs - get(unique-id) to retrieve url and put(unique-id) to store in hash, that can be scaled horizontally separately.

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.