DevOps Patterns Guide

This book aims to provide you with a toolbox for the implementation and development of DevOps in your company. I discuss here the most widespread and relevant patterns. The target audience of this book is companies wishing to produce faster while maintaining a very high level of quality. This is the goal of DevOps. It focuses on everything related to the software production chain and is based in particular on the relationships between Devs and Ops. As the CALMS (Collaboration, Automation, Lean, Measurement, and Sharing) model shows, this goes beyond simply using tools.The limitation of the models as presented here is that they are general and are not intended to be implemented as such in all organizations and in the same way. DevOps is in fact inseparable from the Agile approach. Agility needs a minimum of DevOps practices implemented in the enterprise, such as continuous integration or continuous delivery for example. But DevOps also needs Agility to help identify obstacles encountered by teams. In a way, one could say that DevOps is at the service of Agility in organizations using Agile for projects. In reality, both DevOps and Agility are based on the foundations of Lean, hence their common DNA. The choice of models to implement and the way they are implemented also depends on the maturity of the organization and teams in DevOps and Agile practices. This choice should rely heavily on experimentation. This guide is therefore only a starting point and can of course only be very incomplete. But it has the merit of providing an initial inventory. Some of these practices come from my own experiences in the highly regulated context of medical software. Some may therefore be much less relevant for less regulated organizations, but they are still best practices.