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

Key considerations in funding open source projects

As much as we want to consider that all open source projects are the same, investors find pitfalls with that idea. The following considerations and lessons learned will help reduce confusion about which projects are preferable to fund for the organizations who have set funds aside or investors who are likely to invest in open source projects:

  • Community: The open source project is more viable if it has individual and institutional contributors.
  • Project usage: The broad criterion is if the project has actual users.
  • Project license: There are hundreds of open source and free software licenses, each with its own nuances. Check for the most widely accepted and curated list. Two examples are OSI-approved licenses, https://opensource.org/licenses, and Debian Free licenses, a curated list of which is available here: https://www.debian.org/legal/licenses/.
  • Project funding: The projects should maintain information in a transparent...