System requirements

Functional:

List functional requirements for the system

1. user registration and authentication
2. URL shortening
3. URL management
4. URL Expiration
5. Redirect to Original URL

Non-Functional:

List non-functional requirements for the system...

1. system should be able to handle 10,000 URL request per second with a response not more than 100 milliseconds.
2. the system should be able to scale horizontally to handle increased traffic.
3. Availability from (CAP Theorem).

Capacity estimation

for 1 day

Data per url = 100 bytes

total Data for 10,000 URL per second = 10000 * 100 = 1000000 bytes = 1 MB/ second.

for over 5 years:

1 MB/ second * 1500 = 1500MB /second.

database

Assuming insert operation take 1 ms.

insert operations = 10000 inserts/second

request per second = 10000 requests

API design

1. POST /api/shorten

request : {

longUrl : "String"

}

response : {

shortUrl: "String"

longUrl : "String"

}

1. Redirect to Original URL

GET /{alias}

simple get request

response : (HTTP 301 or 302) to original URL

1. GET Url Details

GET /url/{alias}

response{

shortUrl: "String"

longUrl : "String"

clicks : 100,

createdAt: dateTimeStamp

}

1. Delete a URL

DELETE /url/{alias}

Response: {

"message": "URL Deleted"

}

Database design

User table:

user_id

username

password

create_at

shortend_Url table:

url_id

long_url

short_code

user_id

created_at

expires_at

High-level design

You should identify enough components that are needed to solve the actual problem from end to end. Also remember to draw a block diagram using the diagramming tool to augment your design. If you are unfamiliar with the tool, you can simply describe your design to the chat bot and ask it to generate a starter diagram for you to modify...

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?