Skip to content

Release — Senior

Design canary, blue-green, rolling, and ring deployments around blast radius and signal quality. Use expand-contract schemas and mixed-version compatibility. Sign artifacts, record provenance, generate SBOMs, and verify policy before deployment.

Define automatic stop conditions using SLO burn, errors, latency, saturation, and domain correctness. Recovery includes configuration, data, traffic, and queued work—not only binary rollback.

Test yourself

  1. Which rollout strategy fits a stateful service?
  2. What must remain compatible during rolling deployment?
  3. Which canary signal detects semantic failure?
  4. How does provenance reduce response time?

Continue to professional.md.