Download to read offline
Uploaded byJames Governor
Progressive delivery at DevOps World
The document discusses the concept of progressive delivery in the context of CI/CD and DevOps, emphasizing its role in enhancing developer experience and managing deployment complexities. It highlights the importance of decoupling deployment from service activation and suggests that this approach can reduce business risk and improve control over deployment decisions. Additional resources for further reading on the topic are also mentioned.
More Related Content
Similar to Progressive delivery at DevOps World
Progressive delivery at DevOps World
- 1. Progressive Delivery: Beyond CI/CD JamesGovernor @monkchips co-founder
- 4.
- 5.
- 15. Pete Hodgson @ph1at martinfowler.com
- 17.
- 22.
- 27.
- 28.
- 29.
- 30. align Customer Experienceand Developer Experience enhanced A/B testing experimentation and feature flags manage deployment target complexity reduce business risk decouple deployment from service activation Bring the business back into control of deployment decisions Turn pace of software delivery into a service management feature Avoid rollbacks and emergency fixes Deploy!=Release Additional Reading Towards Progressive Delivery by James Governor New Kingmakers, How Developers Conquered The World by Stephen O’Grady, RedMonk – free ebook. Observability Thought Leaders - Charity Majors (@mipsytipsy), Cindy Sridharan (@copyconstruct), Jaana B. Dogan (@rakyll) GitOps - Alexis Richardson, (@monadic) founder of weave.works. What You Need to Know
Editor's Notes
- #3 Some companies are just moving so much faster than others. It’s absurd
- #5 CI/CD is the onramp for everything good in modern software development. Better quality software, built faster.
- #6 Ci/CD is the onramp for everything good in modern software development. Better quality software, built faster.
- #7 But it’s also scary, with an *expectation* of failure
- #8 Debugging in production – needs that kind of automation.
- #9 But what’s the use case? One is canarying
- #10 Or blue green deployments
- #11 feature experimentation
- #12 What’s the blast radius of a new service being rolled out? Can we limit the population?
- #13 Even a blue green deployment can be gradual, complex.
- #14 Even a blue green deployment can be gradual, complex.
- #16 See Peter Hodgson on “feature toggles”
- #18 CI/CD perhaps doesn’t go far enough – Progressive Delivery is what I call the new routing approaches, with feature flags, canarying etc. taking full advantage of container native cloud infrastructures.
- #19 But Kubernetes emerged as the orchestration environment of choice. Ops people bought into the model, and now it’s the defacto standard for all container-based workloads. All major players have adopted it, including Pivotal, Rancher, Mesosphere, VMware, Microsoft, IBM. And of course Docker itself.
- #20 There is no consistent deployment target
- #21 Kubernetes and cloud native – the challenge for long term support (LTS) models
- #22 LTS is dead
- #23 CI/CD perhaps doesn’t go far enough – Progressive Delivery is what I call the new routing approaches, with feature flags, canarying etc. taking full advantage of container native cloud infrastructures.
- #25 Target has invested heavily in people, from 30/70 internal/consultants to 80/20 internal/external, hiring 1000 people in 3 years. Open source agile skills. Also training third parties. The best way to learn is to teach. Open sourcing. K8s native – every store running Kubernetes
- #28 All of this stuff can be rather complex though. Find vendors that can help package related ideas and technologies.
- #29 CI/CD perhaps doesn’t go far enough – Progressive Delivery is what I call the new routing approaches, with feature flags, canarying etc. taking full advantage of container native cloud infrastructures.
- #30 CI/CD perhaps doesn’t go far enough – Progressive Delivery is what I call the new routing approaches, with feature flags, canarying etc. taking full advantage of container native cloud infrastructures.
- #31 concluding