Use Case: Configure scalable and resilient infrastructure using containerization FEA505
It is a good idea to include a view of the selected relevant use case description.
Remember that the drawn description is only part of the description of the use case! The use case should be described in detail in text format.
- Author: Petteri Heinola
- Date / Version: 22/2/2024
User roles
- User
- Administrator
Prerequisites / Conditions
- Server is configured to be scalable
Use Case Diagram
Description of use case -eg. Modify existing request
- Multiple Users do simultaneous requests to application
- Application overloads
- Automation kicks in and creates more containers to handle user loads
- User loads lessen
- Automation removes unnecessary containers
Exceptions
-
E1 Gateway host gets overloaded
-
E2 Error in automation prevents container creation
Result
- System can serve unexpeted, high amounts of traffic without halting and resist application crashes due to programming errors.
Use frequency
- Depending on the volume of traffic, multiple times a day.
Additional information
- In production environment it would be beneficial to run separate gateway host and container hosts, which could be created depending on the volume of traffic.
Sources
This wiki-document is based on the The public administration recommendations
Thans to the original authors.