Standby Pooling Process

Application component instances should be kept on standby to increase provisioning speed and utilize billing time-slots efficiently.

Standby Pooling Process How can defined provisioning times for application component instances be ensured while utilizing pay-per-use resources in an optimal fashion?


Even though application component instances may be provisioned and decommissioned dynamically, it usually requires some time to actually provision and decommission them. If a cloud application, however, experiences drastic and quick workload changes, these provisioning times may limit its capability to obtain the required resources quickly enough. Decommissioning of component instances immediately when no longer needed may also be ineffective, if cloud resources are charged for fixed time-slots.


Instead of decommissioning application component instances instantly when they are unused, they are assigned to a standby list They are decommissioned only when the time-slot they have been paid for has been utilized and they are still not needed. The standby list may always contain a certain number of component instances to ensure timely provisioning.

Standby Pooling Process

Standby Pooling Process

Multi-Component Image, Resiliency Management Process, Feature Flag Management Process