-
Be the first to like this
Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Published on
In today's world, we need not only to maintain our systems running 24x7 in production but we must also be able to keep them releasable 24x7. We can only do that with modern infrastructure and software delivery practices. Releases should be even more boring than doing your supermarket shopping. Make a code change, see it go through the pipeline, get green or red result. If red, fix or rollback. If green, deploy. If deploy fails, rollback. Monitor forever.
Because everyone wants to go faster but also safer, we're cramming more and more activities in the pipeline, from security controls to database changes, to compliance approvals, soon networking... How can we do this AND still move fast AND avoid burning out teams with all this cognitive load?
I will talk about how to ensure that your delivery system serves its core purpose of quickly and safely progressing our client-facing systems from commit to production. You'll also hear about key practices for software releasability like pipeline-as-code, short and wide pipelines, build and release from zero to production, blue-green deployments, and more!
Be the first to like this
Be the first to comment