Most of the examples we saw are Client server interaction in sync or async way so that each request will be processed and result displayed . UI or stored to DB. When client requests are high volume and need more processing time we need to design few systems where requests can be queued and processed. Which can handle scalability interms of software scalability not hardware scalability.
- Here is my first demo component diagram which can introduce queue system and can buffer requests bfeore they can be further processed. Not very accurate interms of component representation but ideas is add requests to service bus and then save to Mongo db and also if required inform clients for real time notifications.
- requests are quees and processed based on priority.
- No request will be lost even if the hardware wont support the huge number of incoming requests.
- So data integrity maintained.
In this example queue processing based on priority and other components to scale up the system and also processing some requests based on priority can be achived. .
Above queing / events / service bus and all components will help to improve the scalability aspects
of the sytem. Here are more dimensions to this one
After all discussion the following could be complex high available modern application design with all components.
We can get more explantion of all blocks from Microsoft or Aws web sites . Baseline highly available zone-redundant app services web application - Azure Architecture Center | Microsoft Learn
No comments:
Post a Comment