Where Are We Going? The Future of Continuous Delivery
summary
Claims that continuous delivery is shifting from many bespoke Rube Goldberg toolchains to three concrete approaches: treat app delivery end-to-end (setup-to-monitoring), run on commodity components (Kubernetes plus hosted services) and use declarative delivery files so platform teams can impose constraints while giving teams graduated freedom. Cites industry signals — Gartner finds organizations moved from about 5 to 25 toolchains — and examples of reusable components like Kayenta and containerized custom stages; Spinnaker is positioned as composable components and pipeline templates, not a monolithic solution.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:33Where are we going
- 4:16Where are we now
- 6:19Challenges
- 7:57Three main challenges
- 8:57Market trends
- 10:06Zoom out
- 11:05Setting it up
- 12:27Centralized approach
- 14:46Declarative
- 15:59Rally Drivers
- 18:06Solving Fat Delivery
- 19:46Commodity Components
- 22:11declarative abstractions
- 23:43Wrap up
related talks
30mModern Continuous Delivery
19mModern Continuous Delivery
24mWhy, What, and How of Continuous Delivery
32mEvent-based Continuous Delivery: The End of the Monolithic Pipeline
55mContinuously Delivering Continuous Delivery
41mAll Things Continuous
42mCONTINUOUS DELIVERY FOR RUBYISTS
52mThe Future of Continuous Delivery