Microservice Continuous Delivery
summary
Case study shows Expedia migrating from many monoliths to microservices and hitting thousands of unmanageable Jenkins pipelines and fragile shared libraries; Codefresh demos a solution built on Kubernetes and Helm with container-based pipelines that run each step in its own image, a single context-aware pipeline triggered per repo, cached shared volumes, and deployment verification via canary deployment and GitOps; measurable wins include lower MTTR and shorter change lead time.
AI-written summary · about
chapters (20)
- 0:00Intro
- 1:05Why microservices
- 4:07Challenges
- 5:47Learnings
- 6:30Traditional Pipelines
- 7:34Scalability
- 8:13Shared Libraries
- 8:46Problems with Shared Libraries
- 10:11Our Approach
- 10:34Our Architecture
- 11:36Containerbased pipelines
- 13:26Open source steps
- 14:00Single pipeline with context
- 15:21Flexible pipeline execution
- 16:14Demo
- 20:25Deployment verification
- 22:31Summary
- 27:27Security
- 28:50QA
- 31:17Hardware requirements
related talks
40mMicroservice Continuous Delivery
52mDeveloping and Continuous Deployment with Microservices
01h 06mContinuous Integration/Continuous Delivery for Microservices: Rule them all
21mWhere’s the Application? Understanding the Challenge of Your Microservice CD Pipeline
38mContinuous Delivery with a Microservices Architecture
26mPivoting your Pipeline from Monolithic to Microservices
27mMicroservices Are ‘Easy’, Dependencies Are Hard
52mThe Future of Continuous Delivery
