System requirements

Functional:

• User can submit a URL and receive a shortened URL.
• The website can maintain the shortened link for 7 days for free users and forever for premium users

Non-Functional:

• The website should shorten the URL within 2 seconds max from the user input.
• The website should support mobile and tablets.

Capacity estimation

• URL Size: 32 bytes.
• Number of users: 3 million per day.
• Number of read requests: 2.5 million per day.
• Number of write requests: 0.5 million per day.

API design

shortenURL(OriginalURL)

Database design

• A single table containing the following fields(userID, originalURL,shortenedURL,accountType)

High-level design

• Client --> Load Balancer --> Server --> Database

Request flows

• The client will open the website enter the URL in a text box then receive the shortened URL.

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

• We will use nodejs with express JS due to their simplicity and powerfullnes for the backend.
• We will use ReactJS for the frontend.

Failure scenarios/bottlenecks

• The database should have replicas.
• The load balancer is used to avoid bottlenecks.

Future improvements

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