A Pocket Guide to Progressive Delivery with GitOps
This handy pocket guide will explain everything you need to know about progressive delivery patterns. Progressive delivery allows developers to control releases and improves delivery reliability. Let’s get you started with a GitOps guide to implementing progressive delivery at scale.
James Governor of Redmonk first introduced the term progressive delivery - a model that includes practices like feature flagging, canary launches, A/B testing, blue-green deployments, and so on. It was met with a lot of excitement as it brought greater control over deployments without compromising on speed. Built on the core tenets of Continuous Integration and Continuous Delivery (CI/CD), progressive delivery enables organizations to release their code faster, reduce risk and negative impact areas, and continuously improve their application quality.
Progressive delivery, however, includes implementation, management, and monitoring of the releases. Taking care of all these critical tasks manually is tedious to say the least. This is why organizations that belong to highly regulated industries would consider progressive delivery risky. Their utmost priority is to avoid failures during releases and ensure security and compliance. With an automated and operationalized approach with Weave GitOps along with Flagger offers, these organizations can now greatly reduce errors during releases by leveraging progressive delivery.
Our pocket guide will give you an overview on how progressive delivery helps you ship code to production with greater confidence. We also take a deeper look at why progressive delivery is perfect for organizations with a low-risk tolerance.
- What is progressive delivery and what are the core elements when implementing it? What exactly does it look like in practice?
- What are the underlying challenges of progressive delivery? Why is GitOps the most ideal development practice to implement progressive delivery?
- Can you implement progressive delivery in a multi cloud ecosystem? How can it be done?
If you’ve considered using progressive delivery to improve the reliability of your releases but were thrown off by all the complexity, this pocket guide is the perfect starting point.