System requirements

Functional:

Given a URL, we'll compress it into a shorter one

Non-Functional:

List non-functional requirements for the system...

Capacity estimation

URL length 2000-3000 characters long

API design

External:

• /shortenURL
• Take in original URL as a parameter
• Hash the URL and store in data base

Database design

Shorted URL Table:

ShortenedURL(Str, PK) -> Hashed from backend

OriginalURL(Str) -> Passed to API from clientside

High-level design

User inputs a URL, clientside sends to server

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

Try to discuss as many failure scenarios/bottlenecks as possible.

Future improvements

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