Loading...
List functional requirements for the system (Ask the chat bot for hints if stuck.)...
This is essential for ensuring only registered users can post comments.
This allows users to participate in discussions.
This is the core functionality, enabling threaded conversations.
This keeps users engaged and informed about new activity.
Users need control over their own comments.
Ensures a safe and healthy discussion environment.
Keeps users informed about relevant replies.
List non-functional requirements for the system...
This service should be highly available.
This service should be highly scalable.
When users publish new comments, the new comments appear within 10 milliseconds.
The service should be highly reliable.
Only registered users can append the messages,others may only read.
The messages will be shown in chronological order in the board messages.
The message can have only text.
Estimate the scale of the system you are going to design...
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?