Microservice and Containerization Patterns > Containerization Patterns > Volatile Configuration
Volatile Configuration (Erl, Naserpour)
How can a container adapt to the unpredictable usage requirements of the microservice it is hosting?

Problem
Solution
Application
A system is implemented within the container that is capable of detecting and dynamically responding to scalability-related changes in hosted microservices and components. Special listener and container configuration writer mechanisms work within the container at runtime to detect scalability changes and then immediately update the container’s configuration file.

The container configuration writer is notified of the need to scale out the container to facilitate the creation of two additional instances of Microservice A.
This pattern can be applied in conjunction with the Service Instance Registration pattern as explained in the complete pattern description.
This pattern is covered in Module 10: Advanced Microservice Architecture & Containerization..
For more information regarding microservice and containerization courses and accreditation,
visit the Microservice Architect Certification program page..