Top 3 Deployment Patterns - From Experience!
summary
Octopus Deploy draws on data from 3,000 customers to recommend three concrete deployment strategies: for SaaS use independently deployable microservices with incremental database migrations, feature flags and versioned inter‑service APIs to get near‑zero downtime and fast rollbacks; for retail group related apps and hit a 4‑hour window per time zone with ~10‑minute store deploys that tolerate poor connectivity; for banks run pipelines per component with approvals, transaction draining and a Chainset rollback to recover to a known state.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 4:50SAS Example
- 11:40CICD Example
- 13:28Finance Example
- 16:00CICD Pipeline
- 17:10Manual Rollout
- 19:00Summary
related talks
44mI Deploy On Fridays
26mThe Many Ways to Deploy Continuously
32mHow Your Deployment Strategy Influences How People Code
40mStrategies for Zero Down Time, Frequent Deployments
47mI Deploy on Fridays (And Maybe You Should Too)
36mAm I Performing Deployments Correctly?
34mDeploying Without Crying: Deployment Strategies for Peaceful Nights
01h 02mContinuous deployment in under 60 minutes with Octopus Deploy