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

Missing parts

In this final section of this chapter, we will shed some light on the missing parts of your delivery strategy and how to deal with them. As you might have noticed, there are lots of technologies and tools out there, all of which have been built based on the ideas and maybe opinions of the people who created them. As the one who designs and/or implements the delivery strategy of your project, you might have a different opinion that doesn’t have to correspond with the tool developer’s opinion. Therefore, it’s natural that the solutions provided might not fit your needs. Here are some examples of such cases:

  • You want to make the developer experience of your platform as easy as possible and you know about the different templating mechanisms, but you are not happy with them
  • You don’t like the opinions people have about promoting applications between stages and want to have a different approach
  • You are not happy with the way the tools...