Volatile Configuration (Erl, Naserpour)
How can a container adapt to the unpredictable usage requirements of the cloud service it is hosting?
When a cloud service scales in, out, up or down in response to runtime usage fluctuations, its underlying container may not be able to keep up and may therefore be subject to runtime exception conditions.
System mechanisms are utilized to keep the container’s configuration in sync with the potentially volatile runtime conditions of its hosted cloud service.
A monitoring mechanism is used to keep track of runtime conditions and a configuration writer mechanism is used to continually update the container’s configuration in response to reported runtime conditions.
Burst In, Burst Out to Private Cloud, Burst Out to Public Cloud, Cloud Authentication, Cloud Balancing, Elastic Environment, Infrastructure-as-a-Service (IaaS), Isolated Trust Boundary, Multitenant Environment, Platform-as-a-Service (PaaS), Private Cloud, Public Cloud, Resilient Environment, Resource Workload Management, Secure Burst Out to Private Cloud/Public Cloud, Software-as-a-Service (SaaS)
The container configuration writer is notified of the need to scale out the container to facilitate the creation of two additional instances of Cloud Service A.