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

Summary

If you would like to start an open source project, this chapter provided you with the key considerations to get you started. As mentioned earlier in the chapter, the project must solve a specific problem, and there are various communities and channels in which you can discuss and collaborate with people to assess the problem statement itself. Once you have built some ideas on how to solve the specific problem, it’s time to think about the next steps. Primarily, every open source project has a project page with a README file that explains how to use your project and also the purpose of the project. Another key aspect is the license, which allows others to use, or modify the source code. As a best practice, you have to add this file to the repo. Examples of popular licenses for open source projects are the likes of MIT and Apache 2.0 GPLv3. Lastly, consider the contribution guidelines or similar artifacts that can help contributors. Software versioning when working on...