SE Radio 585: Adam Frank on Continuous Delivery vs Continuous Deployment

Deployment Concepts

Adam Frank, SVP of Product and Marketing at Armory.io, distinguishes between continuous integration, delivery, and deployment. Continuous integration focuses on producing artifacts through automated tests, while continuous delivery ensures these artifacts are release-ready with manual approvals. Continuous deployment automates the final step, deploying code to runtime environments without manual intervention, supported by safeguards like canary and blue-green deployments 1. Frank emphasizes the importance of these practices in enhancing business agility and improving customer experiences 2.

Continuous deployment is really about automating that last step. So when developers are committing their codes, there's an artifact being created out of their continuous integration process.

--- Adam Frank

These methodologies are crucial for organizations aiming to streamline their software development processes.

   

Deployment Challenges

Continuous deployment presents challenges, especially with tightly coupled services requiring synchronized updates and rollbacks. Adam Frank shares experiences of manual approvals complicating deployments, highlighting the need for automated solutions to manage dependencies effectively 3. In B2C environments, regulatory constraints add complexity, necessitating manual checks to ensure compliance before updates 4.

There are solutions out there, ours included, that enables you to automatically update tightly coupled services and roll back tightly coupled services as needed.

--- Adam Frank

These challenges underscore the importance of strategic planning and robust infrastructure to support continuous deployment.

   

Approval Processes

Approval processes in CI/CD vary between continuous delivery and deployment, with the latter eliminating manual interventions. Adam Frank notes that prerequisites like continuous integration are essential for effective deployment, ensuring artifacts are ready for production 5. The choice between continuous delivery and deployment often depends on business models, such as B2B versus B2C, where different levels of automation and manual checks are required 2.

You can have the integration test run, and then you can click the approve button and have that continue on to the next environment or the next stage within your overall deployment.

--- Adam Frank

Ultimately, organizations must tailor their CI/CD processes to align with their unique goals and operational needs.