Releases, Canarying and Launch Readiness

Change is the biggest source of outages. Make each change small, gradual, observable and reversible, and make launches repeatable and boring.

Releases, Canarying and Configuration

Change is the biggest source of outages. Make change small, gradual, observable and reversible.

Release engineering principles

• Self-service — teams release on their own cadence through a shared, automated pipeline.
• High velocity — frequent small releases are easier to debug and roll back than big ones.
• Hermetic, reproducible builds — same inputs give the same binary regardless of machine; pinned toolchains and dependencies.
• Enforced policy — code review, who may release, which tests must pass; all audited.
• Every release is identifiable (version visible in monitoring) and rollback is one command, tested regularly.

Canarying procedure

A canary exposes a small part of production to the change and compares it against a control before going further.