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:

• Availability: Higher availability of short to long url query comparing to creation.
• Latency: Lower latency on short to long url query. Average latency on mapping creation.
• Scalability: High traffic on short to long url query comparing to creation.

API Design

Concept (data)

shortUrl

• id
• code (The shorten url. For simplicity, we can use string id as code)
• destination (the origin long url)
• Owner
• LastUpdatedBy
• LastUdpatedDate
• CreatedDate

RESTful API - api/v1/

1. POST shortUrls/
2. GET shortUrls/{id} // id is equal to shortUrl
3. GET shortUrls/by-code/{code} // when id cannot be shortUrl
4. GET shortUrls/{id}?fields=destination
5. PATCH shortUrls/{id}
6. DELETE shortUrls/{id}

High-Level Design

The long url -> short url mapping is stored in a database.

There is an API layer responsible for the operation of the mappings.

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.