Hands-On Microservices with Kubernetes

When is dynamic configuration useful?

Dynamic configuration is useful in the following cases:

• If you just have a single instance of your service, then restarting means a mini-outage
• If you have feature flags that you want to switch back and forth quickly
• If you have services where initialization or dropping in-flight requests is expansive
• If your service doesn't support advanced deployment strategies, such as rolling updates, or blue-green or canary deployments
• When redeploying a new configuration file may pull in unrelated code changes from source control that are not ready for deployment yet