Immutable infrastructure

How to use the concept

Start by writing down the event that begins the clock, the event that ends it, and the population that belongs in the denominator. For immutable infrastructure, this boundary matters because retries, approvals, parallel work, and excluded services can otherwise change the result without changing the underlying workflow.

A concrete delivery example

Consider two services with the same immutable infrastructure value. One serves a small internal workflow and the other handles a public checkout path. Their numbers may be numerically comparable but operationally different, so the team should inspect volume, severity, user impact, and release mechanisms before drawing a conclusion.

Limitations and interpretation

Interpretation requires context. Immutable infrastructure can vary with service architecture, traffic, release strategy, and incident severity. Avoid comparing unlike populations or turning the number into an individual target. Use the result to choose an investigation and revisit the definition when the system changes.

Before acting on immutable infrastructure, compare the current observation with a compatible baseline and ask which underlying event produced it. Keep the raw records, counting policy, and ownership visible. When the signal changes, inspect the surrounding workflow for queueing, rework, failed checks, or recovery work. That practice makes the glossary term useful for diagnosis rather than a label attached to a dashboard.