Achieving Consistent, Low‑Cost Environments with Declarative IaC and OAM

The final state of software delivery is a stable, predictable system, which requires both product consistency and runtime environment consistency.

In the third lecture we shift focus from ensuring product consistency to guaranteeing environment consistency, aiming for predictable, stable, low‑cost environments.

Environment Management Stages

Stage 1: Documentation – Traditional deployment manuals often become outdated and incomplete, leading to on‑site verification.

Stage 2: Commands – Scripts (shell, Python) automate environment setup, but proliferating scripts increase maintenance overhead.

Stage 3: Declarative Definition – Configuration files express the environment, providing deterministic, version‑controlled definitions.

Kubernetes Example

Kubernetes consists of a master (scheduler, controller‑manager, API server, etcd) and nodes running multiple pods. Pods are the smallest unit, containing containers and associated resources; declarative pod specifications are applied and processed by controllers.

Sidecar Pattern for Concern Separation

Business code coexists with service‑governance code (logging, monitoring, rate‑limiting, circuit‑breaking). By placing governance components in sidecar containers, developers focus on business logic while SREs manage the sidecars, enabling independent upgrades.

Too Many Configuration Items – Managing with IaC

Infrastructure‑as‑Code (IaC) treats the entire environment, including middleware resources, as code. Configurations (application, operations, infrastructure) are stored in repositories, enabling consistent, versioned deployments.

Challenges of IaC

Flexibility introduces complexity: loosely coupled text configurations lack a unified aggregate, leading to hidden dependencies and runtime conflicts. Additionally, the learning curve is steep for developers unfamiliar with operational policies.

To mitigate these issues, Alibaba and Microsoft introduced the OAM model, aggregating all IaC resources per application and separating roles (application developers, operators, infrastructure maintainers), thus simplifying management and reducing learning costs.

In summary, the ultimate goal of environment management is an immutable, software‑defined environment, best realized today through an OAM‑based, application‑centric IaC approach.