Loading...
List functional requirements for the system (Ask the chat bot for hints if stuck.)...
The users can capture a screenshot, store it, and send it.
The users can download their own screenshots made earlier
The users can assign tags to a screenshot.
Users can share screenshots with their friends to view them.
The users can change the size of images and its properties before uploading.
The users can remove their screenshots.
List non-functional requirements for the system...
We should have the client applications for web, mobile, and desktop.
If users upload a new screenshot, it will be available in 100 milliseconds.
Users may choose the users with whom they share the screenshots or make a screenshot public.
The platform should be designed to handle a high number of concurrent users efficiently. This might involve implementing techniques like load balancing and caching to distribute requests and minimize response times.
The system architecture should allow for horizontal scaling to accommodate increasing user traffic and data volume. This could involve using distributed databases and cloud-based infrastructure.
User data, including passwords and personal information, should be securely stored using encryption techniques.
The user interface (UI) should be intuitive and user-friendly for both novice and experienced users. A clean and well-organized UI with clear navigation elements will enhance user experience
Estimate the scale of the system you are going to design...
Here's the calculation for storage requirements based on the provided assumptions:
Therefore, based on the assumptions, the estimated storage requirement for the system would be around 770 Peta Bytes per year.
Define what APIs are expected from the system...
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...
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?