Configuration management
Configuration management is the systematic practice of defining, tracking, and controlling system and application settings and their changes throughout their lifecycle.
100 SQL Server Mistakes and How to Avoid Them
Configuration management is the practice of maintaining systems in a known, consistent, and compliant state throughout their lifecycle.
- How it is used
- Maintains SQL Server and operating-system configuration in a known, compliant state throughout the application lifecycle.
- How deep it goes
- Explains build-time automation, periodic evaluation, drift correction, and resource test/set methods, but does not detail every resource.
- Examples
- Uses an enabled xp_cmdshell vulnerability, a 30-minute evaluation interval, and PowerShell DSC SQL installation listings.
- What you can do after
- Operate/configure SQL Server installations with automated desired-state enforcement and correction of post-deployment drift.
Read how 100 SQL Server Mistakes and How to Avoid Them explains configuration management →
Acing the CCNA Exam: Volume 2 Advanced Networking and Security
Configuration management is the systematic process of defining, applying, tracking, and enforcing the configurations of devices or other infrastructure.
- How it is used
- Scales network configuration by standardizing, deploying, tracking, and enforcing device settings through automation.
- How deep it goes
- Explains standards, templates, centralized servers, configuration drift, and enforcement, then compares major automation architectures.
- Examples
- Uses DNS, NTP, routing, QoS, AAA, security, logging, monitoring, and Puppet service declarations as configuration examples.
- What you can do after
- Operate/configure it by applying standardized device states, automating changes, and enforcing consistency with infrastructure-as-code tools.
Spring Microservices in Action
The practice of managing configuration settings for services across their deployment and operation.
- How it is used
- Supports consistent microservice deployment across environments without manually configuring each instance.
- How deep it goes
- Explains four architectural principles and the bootstrap, versioning, deployment, and refresh activities that put them into practice.
- Examples
- Uses database and middleware connection settings and compares source-controlled files, relational databases, and key-value stores as repository options.
- What you can do after
- Evaluate configuration architectures against separation, abstraction, centralization, and availability principles.
Read how Spring Microservices in Action explains configuration management →
Designing AI Systems
Configuration management is the controlled handling of application settings, secrets, and environment-specific values across system operation.
- How it is used
- Supports production AI platforms by controlling secrets and environment-specific settings as systems grow beyond prototypes.
- How deep it goes
- Defines the operational role of configuration management but stops short of implementation details, schemas, or deployment procedures.
- Examples
- Uses environment settings and secrets as configuration concerns, contrasting production foundations with a prototype that failed at 50 concurrent users.
- What you can do after
- Operate scalable application infrastructure with secrets and environment settings handled as shared platform concerns.
Read how Designing AI Systems explains configuration management →
Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
The practice of maintaining systems in a defined configuration state across their lifecycle.
- How it is used
- Maintains desired server and resource states while supporting infrastructure testing, updates, security, and operational tuning.
- How deep it goes
- Defines fleet configuration, gives refactoring and recovery procedures, and defers detailed guidance for individual tools.
- Examples
- Uses 10,000-server package updates, modular refactoring, and package-version reversion as operational examples.
- What you can do after
- Operate configuration tools to enforce fleet-wide package states, refactor automation, and recover servers through forward changes.
Also covered in
- Amazon Web Services in Action, Third Edition: An in-depth guide to AWS
- gRPC Microservices in Go
- Shipping Go: Develop, deliver, discuss, design, and go again
- Think Like a Software Engineering Manager
- ScyllaDB in Action
- Architecting an Apache Iceberg Lakehouse
- Learn Docker in a Month of Lunches, Second Edition
- Data-Driven Cybersecurity
What to know first
- deployment pipelineA deployment pipeline is a repeatable sequence of stages that builds, tests or validates, packages, and delivers software changes toward release or deployment.
- automationAutomation is the execution of tasks or processes by machines or software with reduced direct human intervention.
- serverA server is a computer system or software process that provides data, resources, or services to other systems, typically by responding to requests.
- productionProduction is the live operational setting in which a deployed software system serves its intended users or processes real workloads.
Related concepts
- configurationconfigures · Configuration is a set of settings or structural choices that specifies how a system, application, or component is organized or operates.
- deployment pipelineuses · A deployment pipeline is a repeatable sequence of stages that builds, tests or validates, packages, and delivers software changes toward release or deployment.
- immutable collectioncontrasts with · An immutable collection is a collection whose contents cannot be changed after it is created.
- microservice architectureconfigures · Microservice architecture is a software architectural style that structures an application as independently deployable services, typically organized around focused capabilities and communicating through defined interfaces.
- driftaddresses · Drift is a change or divergence over time in a system’s data, state, behavior, or performance relative to a reference or intended condition.
- dynamic configuration managementincludes · Dynamic configuration management is the automated provision, selection, and alteration of application or infrastructure configuration as environments and requirements change.
Questions about configuration management
What is configuration management?
Configuration management is the systematic practice of defining, tracking, and controlling system and application settings and their changes throughout their lifecycle.
Which Manning books explain configuration management?
100 SQL Server Mistakes and How to Avoid Them, Acing the CCNA Exam: Volume 2 Advanced Networking and Security, Spring Microservices in Action, Designing AI Systems and Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform.
What should I know before learning configuration management?
Manning books that teach configuration management usually introduce deployment pipeline, automation, server and production first.
What is the difference between configuration management and immutable collection?
Configuration management is the systematic practice of defining, tracking, and controlling system and application settings and their changes throughout their lifecycle. An immutable collection is a collection whose contents cannot be changed after it is created.
What kinds of configuration management are there?
Kinds of configuration management include dynamic configuration management.
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.




