List functional requirements for the system (Ask the chat bot for hints if stuck.)...
convert full url to short ones.
when user try to access short URL, the system will access full URL which short url represents.
List non-functional requirements for the system...
scalability: need support this feature all over the world and serve 1b users.
availability: high availability to make sure
performance/latency: need get short ulr in 100ms and convert short to regular url in 10ms?
accuracy: make sure user to get right regular url from short
consistence: we dont need it?
Estimate the scale of the system you are going to design...
assuming:
short: 8B
long: 128B
ownerID: 32B
createTime: 8B
expired Time: 8B
192B ~ 256B
200 /s: five years: 200*60*60*24*365*5*256=8TB
Define what APIs are expected from the system...
shortenURL(str long_url, user_ID, expiration_time=None): Takes a long URL and returns a short URL.
redirectURL(str short_url): Takes a long URL and returns the associated long URL.
Defining the system data model early on will clarify how data will flow among different components of the system. Also you could draw an ER diagram using the diagramming tool to enhance your design...
key-value database
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...
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...
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...
Explain any trade offs you have made and why you made certain tech choices...
Try to discuss as many failure scenarios/bottlenecks as possible.
What are some future improvements you would make? How would you mitigate the failure scenario(s) you described above?