Deployment Procedure

All service deployments use progressive rollout: build artifact, run smoke tests, deploy to staging, run contract tests, deploy canary to 5 percent, monitor for 20 minutes, then continue to 50 and 100 percent.

Checkout deployments require additional validation of cart creation, inventory reservation, and billing authorization. Authentication deployments require JWKS validation and token refresh smoke tests. Billing deployments require idempotency replay tests.

Rollback is preferred when error budget burn exceeds 2 percent in 30 minutes, p95 latency doubles, or critical business transactions fail.