Where’s the Application? Understanding the Challenge of Your Microservice CD Pipeline
summary
Microservice CD breaks the notion of a single application version and CI shifts to creating container images and registries rather than one big binary; continuous delivery must track thousands of independently deployable components across clusters. Expect surprising numbers: ~15% report massive success, organizations hit trouble around ~40-microservice tipping point, while Netflix/Amazon run thousands of microservices. Essential artifacts are BOM and diff reports with impact analysis and tooling like Spinnaker, Tekton, registries (Harbor/Quay) and config managers such as Ortelius or DeployHub to reassemble the logical application.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:32Who is Tracy Ragan
- 3:46microservices are taking over
- 14:03microservices are constantly changing
- 14:35application version tracking
- 15:39software configuration management
- 16:04open source tools
- 16:47what it will look like
- 19:24benefits
- 20:16outro
related talks
40mMicroservice Continuous Delivery
01h 06mContinuous Integration/Continuous Delivery for Microservices: Rule them all- 40mMicroservice Continuous Delivery
26mPivoting your Pipeline from Monolithic to Microservices
45mContinuously delivering containerized, highly available microservices
38mContinuous Delivery with a Microservices Architecture
27mMicroservices Are ‘Easy’, Dependencies Are Hard
30mModern Continuous Delivery