Architecting for Continuous Delivery
summary
Covers architectural principles and patterns that enable Continuous Delivery at internet scale, focusing on how to change system architecture (not just culture) to support faster, more reliable deployments. Describes concrete approaches for incrementally evolving existing systems to make them deployable using DevOps and Continuous Delivery practices.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:21microservices
- 1:55what is continuous delivery?
- 5:48ingredients
- 7:07deployment pipeline
- 9:18to validate golden rules
- 12:06internet architecture
- 13:27component / service
- 15:09conway's law
- 16:21one team per service
- 18:16Bind Components at Run Time (us)
- 21:18Bind Components at Build Time
- 23:28Unreliable Platform
- 30:57Strangler Application
- 33:50devops benchmarking
related talks
19mModern Continuous Delivery
38mPractices for Effective Continuous Software Architecture
51mBetter software, faster: principles of Continuous Delivery and DevOps
24mWhy, What, and How of Continuous Delivery
25mContinuous Delivery Design Patterns
30mModern Continuous Delivery
59mWhy Continuous Delivery doesn't work?
55mThe Rationale for Continuous Delivery
