AdvancedProduction & Delivery

Lab: ship safely

Make the delivery calls — deployment strategy, rollback, config, and secrets.

Lab · optionalFundamentalsAdvanced9 min

Recommended first

By the end of this lesson you will be able to:

Optional scenario lab. Delivery is a series of judgment calls under pressure. Practice them here.

1.
A deploy you just shipped broke production. Fastest mitigation?
Find the root cause first, then actRoll back the deployAdd more logging and redeployRestart servers at random
2.
Releasing a change to a small slice of users first, watching metrics, then widening, is a:
Blue-green deploymentCanary releaseRolling deploymentBig-bang release
3.
An API key was committed to a private repo months ago. It should be treated as compromised and rotated.
TrueFalse
4.
The same build artifact runs in dev, staging, and prod. What should differ between them?
Rebuild the code per environmentOnly the configuration (e.g. environment variables)Hand-edit the code in eachNothing at all

The throughline: make rollback trivial, ship in small blast radii, and keep config and secrets outside the code.

Finished reading? Mark it complete to track your progress.

Configuration and environments

Separate config from code so one artifact runs anywhere — safely.

Logging, metrics, and tracing

The three pillars that let you see what a running system is actually doing.