Engineering / advanced
Delivery systems with controlled risk
Tie artifact promotion, staged exposure, rollback, migrations, and policy evidence to explicit release safety properties.
Your route through engineering
Follow the path or begin with a question. Every lesson is open.
Your place, at your pace. Progress is optional and saved only in this browser when available.
Read / explore / reason
Inside this module
Module 01 advanced
Delivery systems with controlled risk
Tie artifact promotion, staged exposure, rollback, migrations, and policy evidence to explicit release safety properties.
- 01
Immutable artifact promotion
Promote a tested content identity across environments while recording configuration separately and preserving the evidence needed to reproduce a release decision.
25 min - 02
Deployment state machines
Model desired state, observed evidence, guarded transitions, and crash recovery so retries do not create duplicated or unsafe release effects.
25 min - 03
Canary analysis and guardrails
Limit exposure with explicit health criteria while accounting for sample size, comparison bias, repeated decisions, and missing telemetry.
25 min - 04
Blue-green traffic cutover
Switch between deployment pools while accounting for routing propagation, active sessions, capacity, and shared durable state.
25 min - 05
Feature flags and lifecycle management
Separate deployed code from exposed behavior while managing stable cohorts, stale configuration, defaults, observability, and flag removal.
25 min - 06
Expand-contract database migrations
Separate additive schema preparation, compatible application rollout, verified backfill, and destructive cleanup so old and new versions can coexist deliberately.
25 min - 07
Rollback compatibility and forward recovery
Choose recovery from the current durable state rather than assuming an older binary, restored snapshot, or inverse migration automatically recreates a safe system.
25 min - 08
Release provenance and attestations
Verify who made a scoped statement about which artifact, then evaluate its claims under a target policy without confusing authenticity with code correctness.
25 min - 09
Deployment freezes and risk budgets
Use a defined reliability budget and release policy to pause routine exposure, preserve recovery paths, and make bounded exceptions auditable.
25 min - 10
Delivery-system failure rehearsals
Inject bounded failures around release decision points and validate independent safety, recovery, and data-integrity oracles rather than merely watching a controller restart.
25 min