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

Why is velocity important?

By delivering our software more often, we can provide lots of benefits to our customers and our business. In this section, we will discuss some of these benefits. When building features for our customers, we always have a vision in mind of how the feature will be used and how it will benefit the customer. Along the way, there are many technicians, but they might not be the ones who are using the feature. As a result, the following things might happen:

  • The feature is technically perfect, but not intuitive: Historically, some things were built in a technically perfect way but were not intuitive for the user and therefore failed.
  • This was not what the customer wanted: Customers might not know exactly what they want, and when asking them, they might not be able to describe it. Therefore, a feature could look like it was built for the customer, but in reality, it was not what the customer wanted.
  • The feature is used in a way that was not intended...