Book Image

Strategizing Continuous Delivery in the Cloud

By : Garima Bajpai, Thomas Schuetz
Book Image

Strategizing Continuous Delivery in the Cloud

By: Garima Bajpai, Thomas Schuetz

Overview of this book

Many organizations are embracing cloud technology to remain competitive, but implementing and adopting development processes while modernizing a cloud-based ecosystem can be challenging. Strategizing Continuous Delivery in Cloud helps you modernize continuous delivery and achieve infrastructure-application convergence in the cloud. You’ll learn the differences between cloud-based and traditional delivery approaches and develop a tailored strategy. You’ll discover how to secure your cloud delivery environment, ensure software security, run different test types, and test in the pre-production and production stages. You’ll also get to grips with the prerequisites for onboarding cloud-based continuous delivery for organizational and technical aspects. Then, you’ll explore key aspects of readiness to overcome core challenges in your cloud journey, including GitOps, progressive delivery controllers, feature flagging, differences between cloud-based and traditional tools, and implementing cloud chaos engineering. By the end of this book, you’ll be well-equipped to select the right cloud environment and technologies for CD and be able to explore techniques for implementing CD in the cloud.
Table of Contents (18 chapters)
1
Part 1: Foundation and Preparation for Continuous Delivery in the Cloud
6
Part 2: Implementing Continuous Delivery
11
Part 3: Best Practices and the Way Ahead

Continuous integration

As described in Chapter 1, continuous integration (CI) is the process of building, testing, and packaging your code automatically in a workflow/pipeline-based way. The process is and should be triggered by every change in the code base, either by the execution of a webhook or periodic watching of the git repository. As an example, developers push changes to the respective feature branch in their code repository. The CI pipeline is triggered and builds the code, runs different levels of tests, and gives feedback to the developers. Here are some things to consider throughout the process:

  • Performance: Developers should get feedback as fast as possible, but they want to get as much confidence in their code as possible. Therefore, it is instrumental to decide which tests should run at which time in the pipeline and how long it takes to execute the tests. Furthermore, it is always important to define the scope of each build. For example, there might be multiple...