System requirements

Functional:

Ability to take the url and return a shorter version of the url

Non-Functional:

• The service should be available all the time
• We want to provide minimum overhead as possible.
• Should be available in multiple region across the world.

Capacity estimation

Estimate the scale of the system you are going to design...

• System should support 100 reads per second and maybe 1 write per second.
• If we have 100 reads per second , system should be hosted on different places we might think of scaling the system.

API design

So we can have two API's , First one would be to create a GET Request which can have url like below:-

co.me/url-short-link

The API , can have 200 success status code and 404 if something went wrong

We may also want to ensure that API are encoded and malicious content request should be denied.

Database design

For DB we can have a no-sql DB that will not have scalability issues. Can store in key value pair fashion.

High-level design

We are going to have a design in which the API would call the load balancer which would redirect it to API gateway from there request would come to the application server.

The application server will check if the request is present in the in-memory cache else we can make a call to DB to get the

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?