System requirements
Functional:
- File Upload: Users should be able to upload files to the service.
- File Download: Users should be able to download files that they have uploaded.
- File Sharing: Users should be able to share files with other users via links.
- File Synchronization: Changes made to files on one device should be synced across all devices.
- Access Control: Users should have the ability to set permissions on who can view or edit their files.
Non-Functional:
- Performance: The system should be able to handle a certain number of concurrent users, e.g., support 10,000 concurrent uploads without latency.
- Scalability: The architecture should support horizontal scaling to accommodate an increasing number of users.
- Security: User data must be protected with encryption, and user authentication should be secure.
- Availability: The system should have an uptime of 99.9%, ensuring that users can access their files whenever needed.
- Usability: The user interface should be intuitive, allowing users to easily navigate and utilize the features.
Capacity estimation
Estimate the scale of the system you are going to design...
API design
Define what APIs are expected from the system...
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?