@jezhumble continuous delivery

@jezhumble continuous delivery: why, what, principles building quality in principles and patterns for low-risk releases overview

@jezhumble what is continuous delivery? The ability to get changes—features, configuration changes, bug fixes, experiments—into production or into the hands of users safely and quickly in a sustainable way.

@jezhumble increase software quality and stability make releases painless, low risk events reduce time to market increase customer and employee satisfaction reduce cost of ongoing software development why continuous delivery?

scrum- fall water-

@jezhumble Jon Jenkins, “Velocity Culture, The Unmet Challenge in Ops” 2011 | http://bit.ly/1vJo1Ya

“Evaluating well-designed and executed experiments that were designed to improve a key metric, only about 1/3 were successful at improving the key metric!” do less “Online Experimentation at Microsoft”, Kohavi et al | http://stanford.io/130uW6X

@jezhumble computers do repetitive tasks, people solve problems build quality in work in small batches everyone is responsible relentlessly pursue continuous improvement key principles

@jezhumble releasing frequently John Allspaw: “Ops Metametrics” http://slidesha.re/dsSZIr

@jezhumble optimize for mtrs

@jezhumble agile manifesto Our highest priority is to satisfy the customer through early and continuous delivery of valuable software

@jezhumble production-ready software Fast, automated feedback on the production readiness of your applications every time there is a change — to code, infrastructure, or configuration.

@jezhumble build quality in “Cease dependence on mass inspection to achieve quality. Improve the process and build quality into the product in the first place” W. Edwards Deming

@jezhumble architecture patterns and practices collaboration continuous delivery

@jezhumble configuration management continuous integration automated testing ingredients

Mainline Server Develop Build Build pull Local Workstation Build push ✔ Done!

Mainline Server Develop Build Build pull Local Workstation Build push ✔ Done! Everyone Commits To the Mainline Every Day

@jezhumble continuous integration at scale Jason Leyba | http://queue.acm.org/blogposting.cfm?id=78323

John Penix | “Large Scale Continuous Testing in the Cloud” | http://bit.ly/1BYMf70

@jezhumble Different Kinds of Testing Diagram invented by Brian Marick

@jezhumble deployment pipeline

@jezhumble Trade Offs

low risk releases are incremental blue-green deployments canary releases dark launching production immune system feature toggles For more on these patterns, read http://bit.ly/low-risk-releases

@jezhumble STATIC CONTENT /static/1.1 /static/1.0 DEPENDENT SERVICE 1.0 1.1 Abstraction layer Abstraction layer APPLICATION Database Router / Load balancer Interwebs expand / contract For more on this pattern, read http://bit.ly/low-risk-releases

@jezhumble incremental db change address address1 address2 address address1 address2 315 montgomery st, 16th floor null null address address1 address2 1 market st, 30th floor 1 market st 30th floor

blue-green deployments For more on this pattern, read https://martinfowler.com/bliki/BlueGreenDeployment.html

router web server app server DB server For more on this pattern, read https://martinfowler.com/bliki/BlueGreenDeployment.html

router v1.1 v1.1 v1.1 web server app server DB server For more on this pattern, read https://martinfowler.com/bliki/BlueGreenDeployment.html

router v1.1 v1.1 v1.1 web server app server DB server v1.2 v1.2 v1.2 For more on this pattern, read https://martinfowler.com/bliki/BlueGreenDeployment.html

router v1.1 v1.1 v1.1 web server app server DB server v1.2 v1.2 v1.2 For more on this pattern, read https://martinfowler.com/bliki/BlueGreenDeployment.html

@jezhumble canary releasing For more on this pattern, read http://bit.ly/low-risk-releases

release != deployment

[featureToggles] wobblyFoobars: true flightyForkHandles: false Config File ... various UI elements some.jsp forkHandle = (featureConfig.isOn(‘flightlyForkHandles)) ? new FlightyForkHander(aCandle) : new ForkHandler(aCandle) other.java Feature Toggles For more on this pattern, read https://martinfowler.com/articles/feature-toggles.html

dark launching For more on this pattern, read http://bit.ly/low-risk-releases

@jezhumble For more on this pattern, read http://bit.ly/low-risk-releases

@jezhumble For more on this pattern, read http://bit.ly/low-risk-releases

Branch by Abstraction For more on this pattern, read https://martinfowler.com/bliki/BranchByAbstraction.html

Application New Library Library For more on this pattern, read https://martinfowler.com/bliki/BranchByAbstraction.html

Application New Library Library Interface implements For more on this pattern, read https://martinfowler.com/bliki/BranchByAbstraction.html

Application New Library Library Interface implements For more on this pattern, read https://martinfowler.com/bliki/BranchByAbstraction.html

Application New Library Library Interface implements For more on this pattern, read https://martinfowler.com/bliki/BranchByAbstraction.html

Application New Library Interface implements For more on this pattern, read https://martinfowler.com/bliki/BranchByAbstraction.html

For more on this pattern, read https://martinfowler.com/bliki/BranchByAbstraction.html

Jesse Robbins, “Master of Disaster” @ Amazon| @jesserobbins | http://oreil.ly/1HRKUVE ”don’t fight stupid make more awesome!”

thank you! © 2016-7 DevOps Research and Assessment LLC https://devops-research.com/ To receive the following: • 30% off my new video course: creating high performance organizations • 50% off my CD video training, interviews with Eric Ries, and more • A copy of this presentation • A 100 page excerpt from Lean Enterprise • An excerpt from The DevOps Handbook • A 20m preview of my Continuous Delivery video workshop Just pick up your phone and send an email To: jezhumble@sendyourslides.com Subject: devops