Continuous Delivery Design Patterns
summary
Claims that CI/CD should move from reference architectures to a catalog of concrete design patterns: four initial patterns — structural creational behavioral domain-driven — each maps to specific problems, tooling and layers (common components, pipeline, deployment). Uses examples like CD Events for behavioral patterns and cites CDF and AWS reference work. Promises measurable benefits: higher pipeline reuse, easier instantiation, improved traceability and observability, lower admin cost and clearer shared responsibility for regulated and cloud environments.
AI-written summary · about
chapters (5)
- 0:00Introduction
- 6:03Why CD matters
- 11:25Design patterns in CI/CD
- 18:51Measuring CI/CD value
- 23:49Future of CI/CD
related talks
13mLightning Talk - CI/CD Patterns
34mArchitecting for Continuous Delivery
18mDesign Patterns For Efficient DevOps Processes
37mAdding Design to DevOps
40mSustainable Continuous Delivery: Patterns for rapid and reliable Releases
01h 05mTwelve Essential Practices to be Effective in Continuous Delivery
30mModern Continuous Delivery
40mContinuous Delivery Anti-Patterns