Environment Strategy
How many environments earn their cost, what each proves, and what none of them prove.
5 to work through
-
intermediate
An organisation has development, integration, staging, pre-production and production environments, and bugs still reach production. What should change?
2 min answer -
intermediate
An organisation maintains many long-lived environments and they have all drifted from production. What environment strategy works?
2 min answer -
intermediate
Six teams share one integration test environment. Bookings are made a week ahead and releases slip when someone overruns. How do you fix it?
1 min answer -
intermediate
Six teams share one staging environment. Booking it is a bottleneck and it is permanently broken by whoever deployed last. Design a way out.
2 min answer -
intermediate
You have one quarter to delete the shared staging environment that eight teams deploy into. Sequence the work so each step is reversible, say where the point of no return actually is, and name what cannot move.
3 min answer
2 terms in this topic
Environment Ladder
The ordered set of environments a change climbs, where each rung is justified by a distinct claim it can prove that the one below cannot.
practiceEnvironment Strategy
The deliberate choice of how many pre-production environments exist, what each is for, and how faithfully each mirrors production.
1 artifact you would hand over
Neighbouring topics
Delivery & Release Engineering
General material on getting a change from commit to production safely and often.
Pipeline Architecture
Stages, fan-out, caching, and the difference between a pipeline and a long script.
Build Reproducibility
Pinned inputs and hermetic builds, so one commit cannot produce two different artifacts.
Artifact Management
Immutable versioned outputs, promotion between repositories, and retention policy.
Branching Models
GitFlow, trunk and release branches as delivery constraints rather than Git preferences.
Continuous Integration Discipline
Integrating to the mainline daily, and the test speed and review culture that requires.
Deployment Strategies
Rolling, blue-green, canary and shadow, and the traffic and state each one assumes.
Progressive Delivery
Separating deploy from release, and exposing a change to users in controlled increments.
Rollback & Forward Fix
When reversing is genuinely possible, and designing so that it usually is.
Database Migration Under CD
Expand-contract, backwards-compatible schema change, and migrations that cannot roll back.
GitOps
Declared desired state in version control, with a reconciler closing the gap continuously.
IaC Modules & Drift
Reusable infrastructure modules, state ownership, and detecting what changed out of band.
Policy as Code
Encoding standards as automated admission and plan-time checks instead of review comments.
Pipeline Secrets
Short-lived credentials, workload identity, and why the CI system is a prime target.
Supply-Chain Provenance
SBOMs, signed artifacts, attestation, and knowing what actually went into a build.
Deployment Gates
Automated verification between stages, and the difference between a gate and a delay.
Flow Metrics
Work in progress, flow time and flow efficiency — where a change waits rather than moves.
Change Management vs CD
Reconciling CAB-era controls with continuous delivery without pretending either away.
Multi-Region Rollout
Ordering regions, bake time, and stopping a bad change before it becomes global.