Deployment Strategies
Cluster focuses on debates and advice around software deployment practices like rolling, canary, blue-green, and zero-downtime techniques to enable frequent, safe releases without interruptions.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Rolling deployment is a hack imho. Adds complexity and hence yet more potential failure modes.
Don’t they have canary deployments? Such huge updates happen al at once?
I release on Friday, it is not any different than any other day. Canary deployment is the way to go and quick rollbacks makes your life easy
"Don't have a deployment process that takes a day ahead"
Not if you have a competent devops team and a deployment pipeline.
Not a slack employee but worked at a company with similar CD views:(Likely) various groups of people are deploying to production throughout the day. Out of those 100 deploys, an individual is probably only involved in 1 or 2 a day. As soon as you're ready to deploy your code, you queue up and see it all the way through to production along with probably a few other people doing the same thing.The actual "change the servers over to the new production code" process is usually i
Nothing I said implies the user has to find it. With rolling deployments and blue/green strategies, bad changes don't even have the potential to go live.
what is good to use if you need to do a rolling deploy midday without interruption for clients?
Seems reasonable to me? Better to deploy gradually in case the deploy is bad, right?
Going from 1-2 deployments a day to 10 without downtime - Awesome stuff!