So far, Continuous Integration/Continuous Delivery (CI/CD) has been at the centre stage of DevOps Services, steering the modern software development industry forward. However, the current and future demands of the industry require new practices that make the deployment process progressive. By Tapan Vora @cuelogic.
Leveraging a mixed bag of technologies and skills for software development testing and deployment – A/B testing, Feature Flags, Blue-Green deployments, and canarying, to name to a few – it transforms the approach toward service and application delivery. And all this to an extent where deploying a service doesn’t necessarily mean releasing it.
The article further covers:
- Moving fast with control
- Release progressions
- Progressive delegation
- The evolution of Progressive Delivery
- The need for Progressive Delivery
- Key elements of Progressive Delivery
- Canary testing
- Blue-Green deployments
- Feature flags
- A/B testing
- Service Mesh
- Chaos engineering
- Benefits of Progressive Delivery
- Best Practices to Implement Progressive Delivery
Progressive Delivery refers to a new lifecycle of software development that is deployed to ship code faster and at reduced risk. Thus, always delivering on improved customer experience. It is essentially an extension of the core tenets of CI/CD equipped with safeguards and controls that exponentially cut the risk of continually pushing code into production.
Progressive Delivery is poised to change the DevOps ecosystem. Naysayers may denounce it as CI/CD 2.0 but the bottom line is that this system will drive changes released in the future based on data insights and an understanding of your audience’s experiences. Good read![Read More]