Enterprise Delivery Highlights Summary
Every highlight bullet from the 8 pages in this section, gathered on one page and grouped by the page it came from.
- Enterprise delivery optimizes for controlled blast radius at speed - not for caution over velocity
- Decoupling 'deploy' (code reaches production) from 'release' (code reaches users) is the mechanism behind flags, canaries, and progressive rollout
- DORA metrics measure two axes at once - throughput and stability - and neither one alone counts as success
- For most Python APIs, the database migration is the real bottleneck on delivery cadence, not the application deploy
- Semver for libraries; calendar or train for services
- Release notes include migrations and rollback steps
- Freeze windows align with commerce peaks
- Tag images with git SHA, not floating tags
- Change advisory board for high-risk schema work
- Flags default off; server-side evaluation
- Canary measures p95 and error budget, not only 5xx
- Kill switch before rollback when path is isolated
- Sunset flags after 30 days stable
- Same flag SDK in API and workers
- Rollback requires backward-compatible migrations
- Forward-fix when schema is irreversible
- Feature-flag kill is fastest for isolated paths
- Retain N previous image tags for undo
- Document decision criteria in release checklist
- Measure per service, not monorepo vanity totals
- Tag incidents with deploy SHA for accurate CFR
- Lead time ends at prod, not merge to main
- MTTR requires practiced rollback runbooks
- Balance speed with error budget policy
- Hypothesis and success metric defined before launch
- Sticky assignment per user or tenant
- Guardrail metrics abort harmful variants
- Server-side assignment prevents tampering
- Statistical significance before full ramp
- Staging mirrors prod topology and pool sizes
- Secrets never in git; promote via vault/SSM
- Config as code reviewed like application code
- Same lockfile hash across environments
- Promotion pipeline is auditable
- Expand-contract migrations before daily deploy promises
- Canary guardrails on p95 and queue depth
- Feature flags decouple ship from exposure
- DORA per service, not monorepo vanity metrics
- API and worker order documented per schema change
Revisado por Chris St. John·Última atualização: 31 de jul. de 2026