System requirements

Functional:

List functional requirements for the system (Ask the chat bot for hints if stuck.)...

URL Shortening

URL redirection

Edit or Delete

Non-Functional:

List non-functional requirements for the system...

Performance

Scalabilty

Relaibility

Security

Capacity estimation

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

It must be highly scalable which could handle increasing traffic .

Response time is low

API design

Define what APIs are expected from the system...

GET API

GET USER API

CREATE SHORT URL

DELETE SHORT URL

ER DIAGRAM

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.

Cache Failure

hash collision

Future improvements