System requirements

Functional:

• request a shortened URL
• redirect a user to an original URL by a shortened version

Non-Functional:

• shortened URLs lifetime
• cache for redirection
• hashing and collisions

Capacity estimation

• 16B per shortened URL
• 256B per original URL
• 2B per timestamp

API design

• POST body=<normalized-original-url>
• GET query=<shortened-url>

Database design

• NoSql persistent DB, like Reddis.
• Each record would include
• key - shortened URL
• timestamp - date of the creation
• original url

High-level design

Request flows

Explain how the request flows from end to end in your high level design. Also you could draw a sequence diagram using the diagramming tool to enhance your explanation...

Detailed component design

Dig deeper into 2-3 components and explain in detail how they work. For example, how well does each component scale? Any relevant algorithm or data structure you like to use for a component? Also you could draw a diagram using the diagramming tool to enhance your design...

Trade offs/Tech choices

Explain any trade offs you have made and why you made certain tech choices...

Failure scenarios/bottlenecks

• if a user tries to request a redirect to an expired on non-existent shortened URL, we will just return 404

Future improvements

What are some future improvements you would make? How would you mitigate the failure scenario(s) you described above?