Configuration drift
Configuration drift is the unintended divergence of a system’s actual configuration from its intended configuration or from that of equivalent environments over time.
Grokking Software Architecture
Configuration drift is the gradual divergence of a system's actual settings from its intended configuration or from the configuration of equivalent environments.
- How it is used
- Uses configuration drift to diagnose fragile cloud operations and motivate repeatable, immutable deployments.
- How deep it goes
- Defines drift, traces its causes and consequences, and outlines a replacement workflow while distinguishing stateful databases.
- Examples
- Uses manually configured servers, forgotten cloud-console settings, and live security patches as sources of mismatch.
- What you can do after
- Operate/configure application infrastructure by rebuilding patched servers from code and switching traffic instead of editing live machines.
Read how Grokking Software Architecture explains configuration drift →
Spring Microservices in Action
The unintended divergence of a system’s configuration from its intended or consistently maintained state.
- How it is used
- Uses configuration drift to motivate identical microservice instances and immutable infrastructure.
- How deep it goes
- Explains causes, deployment safeguards, and server replacement, but does not detail provisioning-script syntax.
- Examples
- Uses a staging-only server change that is missed in production and fresh server rebuilds as examples.
- What you can do after
- Operate services with repeatable images by changing provisioning scripts and rebuilding rather than manually editing deployed servers.
Read how Spring Microservices in Action explains configuration drift →
Related concepts
- immutable infrastructureaddresses · Immutable infrastructure is an infrastructure-management approach in which deployed resources are replaced with newly configured resources rather than modified in place.
- infrastructure as codeaddressed by · Infrastructure as code is the practice of defining, provisioning, and managing computing infrastructure through machine-readable code or configuration rather than manual procedures.
- concept driftcontrasts with · Concept drift is a change over time in the data-generating process, including the distribution of inputs or the relationship between inputs and target outcomes.
- driftkind of · Drift is a change or divergence over time in a system’s data, state, behavior, or performance relative to a reference or intended condition.
Questions about configuration drift
What is configuration drift?
Configuration drift is the unintended divergence of a system’s actual configuration from its intended configuration or from that of equivalent environments over time.
Which Manning books explain configuration drift?
Grokking Software Architecture and Spring Microservices in Action.
What is the difference between configuration drift and concept drift?
Configuration drift is the unintended divergence of a system’s actual configuration from its intended configuration or from that of equivalent environments over time. Concept drift is a change over time in the data-generating process, including the distribution of inputs or the relationship between inputs and target outcomes.
What is configuration drift a kind of?
Configuration drift is a kind of drift. Drift is a change or divergence over time in a system’s data, state, behavior, or performance relative to a reference or intended condition.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.

