System requirements

Functional:

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

generate doc

edit doc

share doc with other people

delete doc

different types of doc: word, excel, ppt

export file

Non-Functional:

List non-functional requirements for the system...

high available

should be scalability

eventually consistency

low latency

Capacity estimation

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

1 Million users

about 10% users using the doc per day = 100,000 users

each user will request 10 times per day, each request is 5KB

QPS = 100,000 * 10 / 86,400 = 11.57

API design

Define what APIs are expected from the system...

generate doc

POST /api/generate

input: userId, title, docType

output: docId

edit doc

PUT /api/edit

input: userId, docId, docType

output: 200 is success

4** is failed

share doc with other people

GET /api/share/userId=?docId=?shareTo=?

input: userId, docId, shareTo

output: 200 is success

4** is failed

delete doc

DELETE /api/delete

input: userId, docId, docType

output: 200 is success

4** is failed

export file

POST /api/export

input: userId, docId

output: 200 is success

4** is failed

Database design

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...

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?