Managing configuration dynamically

So far, the configuration options we have discussed have been static. You have to restart and, in some cases (such as with embedded configuration files), redeploy your service to change its configuration. The nice thing about restarting your service when the configuration changes is that you don't have to worry about the impact of the new configuration changes on the in-memory state and the processing of in-flight requests because you're starting from scratch; however, the downside is that you lose all your in-flight requests (unless you are using a graceful shutdown) and any warmed-up caches or one-time initialization work, which could be substantial. You can mitigate this somewhat, though, by using rolling updates and blue-green deployments.

...