Loading...
List functional requirements for the system (Ask the chat bot for hints if stuck.)...
1) The Service should support various statuses like online,idle and offline
2) The services should be updated dynamically
List non-functional requirements for the system...
1) The system should be scalable
2) The System should be fault tolorent
3) The System have very less latency
Estimate the scale of the system you are going to design...
Let's assume the system makes call to get the status after every 5 seconds then total number of calls made in the day =86400/5=17280
if total number of users are 1000,000 then total qps =1000,000 *17280= 1728 * 10 ^7
Define what APIs are expected from the system...
update User Status - /v1/update-status This api update the status of the user it return 200 if the status is updated else will return 500 if it is not able to update the status
Get User Status - /v1/status The following api returns the status of the user
it will return 200 if it is sucessfull else it will return status 500
Get Batch Status - v1/batch-status - The following api returns a batch of status for the user and it will return
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...
As the System is write heavy so we will use casandra as our primary database and it will have the following structure
UserId, Username, Status
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?