To get to CD, applications and delivery pipelines must be architected in a way that supports the more frequent pace of smaller, incremental releases.
This morning on Continuous Discussions, we discussed some recommendations for constructing a flexible, version-able, review-able, test-able, revert-able and resilient application architecture and CD pipeline.
- How do Microservices, service-orientation design in general, and decoupling strategies affect your delivery pipeline?
- What should you take into account when orchestrating your pipeline and the way you manage your environments?
- How to manage database schema changes or messaging as part of architecting oyur app to enable Continuous Delivery?
- and more..
Watch the Replay of this episode:
This episode features:
QA Automation Lead at Wrap Media. Melvin has worked at various start up and enterprise companies developing automated tests and working on CI/CD pipelines. He spends his “free” time speaking at Meetups/Conferences, teaching QA workshops and working on a weekly comic strip, www.melvinisms.com.
@mlaguren | www.laguren.net
Episode 28: Docker and Containers in your CD Pipeline
Join us on November 3rd to discuss architecture patterns and best practices for enabling CD.
This episode will feature:
Continuous Discussions (#c9d9) is a bi-weekly series. See all episodes here.
Latest posts by Sam Fell (see all)
- DevOps Enterprise Summit 2017 top takeaway: Adoption rapidly moving beyond IT - November 22, 2017
- Continuous Discussions (#c9d9) Podcast, Episode 82: Gene Kim and the DOES17 Speakers #5 – The Deployment Age - October 31, 2017
- Join Gary Gruver and Electric Cloud for an Exclusive Workshop for Executives Leading the DevOps Transformation - October 23, 2017