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.)...
  • Since a huma is waiting, we want low latency(sub 200 ms)
  • We prioritize high availability, meaning eventual consistency
  • We are assuming a high read to write ration maybe sth like 100:1
  • We are also assuming cumulative data storage meaning data is permantly growing
  • We are assuming global distributation incase of data center going down. So we want Multi-region replication

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

GET /v1/url/{shorten_url}

{

String long_Url

}

POST /v1/url

{

String long_url

}

Returns shorten_url

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.

Write through, read aside cache to handle freqeuently read URLs and recently created URLs to target sub 200ms latency

We have distinct services for the read and write to seprate these concerns and achieve high throghput

We utilize a SQL database that is sharded by eithe region/consistent hashing or range to scale our write speeds

and we use high level of replications per shard tot maintain high read speeds. We utilize a queue ot handle async data replications with data preservation.