Declarative configuration
Declarative configuration specifies a system’s desired state, structure, or behavior while leaving the steps for achieving it to an executing system or tool.
Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
Infrastructure configuration is the declarative specification of the resources, properties, relationships, and metadata that make up an infrastructure system.
- How it is used
- Uses declarative configuration to communicate architecture, automate infrastructure changes, coordinate teams, and reduce operational error.
- How deep it goes
- Explains composition, sharing, testing, delivery, branching, and refactoring, while emphasizing practices rather than provider-specific implementation.
- Examples
- Uses a hello-world.com production stack, shared vegetable-team modules, network unit tests, branching environments, and a refactored singleton repository.
- What you can do after
- Build it from scratch, compose reusable resources, test configuration statically, collaborate through version control, and refactor safely.
Automating API Delivery
Declarative configuration specifies a system's desired state while leaving a tool or agent to determine and execute the commands needed to achieve it.
- How it is used
- Defines the desired API gateway state used to expose backend services to API consumers.
- How deep it goes
- Defines desired-state configuration, contrasts it with imperative scripts, and demonstrates gateway routing and authentication without detailing the agent’s commands.
- Examples
- Uses Kong YAML and a curl request with Host and x-api-key headers to verify a secured product route.
- What you can do after
- Apply it via Kong to route and secure an API, then verify the gateway request with curl.
Read how Automating API Delivery explains declarative configuration →
Amazon Web Services in Action, Third Edition: An in-depth guide to AWS
A blueprint is a declarative infrastructure specification that describes resources and their configuration.
- How it is used
- Automates repeatable AWS infrastructure creation, modification, and deletion across complex or numerous environments.
- How deep it goes
- Defines blueprint reconciliation and its benefits, but stops short of blueprint syntax or Infrastructure as Code implementation details.
- Examples
- Uses a CloudFormation WordPress stack, network and virtual-machine setup, and reusable AWS blueprints for infrastructure automation.
- What you can do after
- Build it from scratch by describing AWS resources and dependencies in a reusable blueprint for repeatable infrastructure changes.
Google Anthos in Action
A declarative model specifies the desired configuration of resources, leaving the system to determine and perform the actions needed to reach it.
- How it is used
- Uses desired-state declarations to automate application and resource management in Kubernetes and Anthos environments.
- How deep it goes
- Explains manifests, control loops, and replica reconciliation, but stops short of detailed manifest syntax or control-plane internals.
- Examples
- Uses a three-replica deployment, accidental Pod deletion, ReplicaSet recovery, and contrasting kubectl resource commands.
- What you can do after
- Operate Kubernetes deployments by declaring resources and understanding how control loops restore their desired state.
Read how Google Anthos in Action explains declarative configuration →
Acing the Certified Kubernetes Administrator Exam, Second Edition
A declarative approach specifies the desired end state while the system determines the operations needed to reach it.
- How it is used
- Deploys Kubernetes workloads by declaring the desired end state instead of executing imperative commands in sequence.
- How deep it goes
- Defines declarative behavior and demonstrates YAML manifests, but stops short of explaining Kubernetes reconciliation internals.
- Examples
- Uses an nginx Pod manifest and the kubectl create command with its pod-created output.
- What you can do after
- Apply it via kubectl by submitting a YAML manifest to the Kubernetes API.
Snowflake Data Engineering
Declarative database change management specifies the desired state of database objects rather than describing only the sequence of operations needed to reach it.
- How it is used
- Manages Snowflake database changes in continuous-integration pipeline repositories.
- How deep it goes
- Explains desired-state definitions, rollback benefits, SQL commands, rerunnable scripts, and repository organization.
- Examples
- Compares EMPLOYEE table creation, column addition, column removal, and schema-organized SQL scripts.
- What you can do after
- Operate/configure Snowflake objects through versioned, rerunnable definitions and recreate states after partial rollbacks.
Read how Snowflake Data Engineering explains declarative configuration →
Related concepts
- imperative programmingcontrasts with · Imperative programming is a programming paradigm that expresses computation as an ordered sequence of instructions specifying operations, control flow, or changes to state.
- infrastructure as codeused by · Infrastructure as code is the practice of defining, provisioning, and managing computing infrastructure through machine-readable code or configuration rather than manual procedures.
- GitOpsused by · GitOps is an operational approach that uses version-controlled declarative configuration as the source of truth and automation to apply or reconcile system state.
- CloudFormation templateequivalent to · A CloudFormation template is a declarative JSON or YAML document that specifies AWS resources, their configuration, and their dependencies.
- peer reviewused by · Peer review is the assessment of work by knowledgeable colleagues or independent experts to evaluate its quality, correctness, validity, or reasoning and provide feedback.
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.