DevOps & Delivery
10 guidesBuild security, immutable delivery, schema evolution, and infrastructure operations.
DevOps Foundations: Reproducible Builds and Artifact Promotion
Separate source, build inputs, artifacts, and deployment configuration so the release you test is the release you actually operate.
DevOps Foundations: Safe Changes, Health Signals, and Rollback Boundaries
Design a release as a controlled change to code, configuration, and data, with explicit health checks and a recovery plan that matches what can actually be reversed.
Docker Multi-Stage Builds: Optimization Patterns for Production
Multi-stage builds keep the runtime image lean while preserving a fast developer loop. Learn how to separate build dependencies from runtime dependencies without losing traceability or reproducibility.
Production Observability: Signals, Service Objectives, and Useful Alerts
Build an operational view around user-visible latency, traffic, errors, and saturation instead of dashboards full of disconnected metrics.
Reliable CI Pipelines: Fast Feedback Without Hiding Failures
Design CI stages, caches, artifacts, and test boundaries so a green pipeline means something and failures are quick to diagnose.
Delivery Engineering Advanced: Build Caches, Runner Isolation, and Safe Releases
Optimize Docker layers without breaking reproducibility, isolate CI execution, secure image provenance, and deploy compatible schema changes.
Release Safety Advanced: State, Schema Compatibility, and Artifact Trust
Connect immutable infrastructure, safe schema evolution, IaC lock recovery, artifact provenance, and CI isolation into one release discipline.
Incident Timelines: Separate Event Time, Receipt Time, and Clock Evidence
Reconstruct a deployment incident without mistaking log delivery order or clock skew for causal ordering.
Scheduled jobs: separate a logical run from its attempts
Give retries a stable business identity without confusing schedule windows with process start times.
CI workload identity: replace copied cloud keys with scoped claims
Reason about OIDC trust, token audience, job identity, and short-lived cloud credentials.