The Devops Handbook Summary Series

Hello everyone. Back after some time. We are going to start a new series of blog posts aimed at crystallizing the learnings from The Devops Handbook. Let's start without any further ado.

Instead of the usual way of starting with the summary of the first chapter, I attempt to start with the summary of the preface. Let's dive in. Devops Myths The authors aim at helping the readers replicate the DevOps transformations that there were part of and or have observed and also dispel the myths surrounding DevOps

Let's have a look at them.

Myth#1 - DevOps Is Only For Startups

While DevOps practices have been started by web-scale internet companies, the flip side is that they too faced problems associated with traditional organizations like highly dangerous code releases prone to catastrophic failure, not being able to release features fast enough to beat the competition, compliance related concerns, inability to scalef, high level of distrust between Dev and Ops

Myth#2 - DevOps Replaces Agile

Many believe that DevOps is a logical continuation of the Agile. Agile focuses on small teams continously delivering high-quality code to customers and many devops came out from that point of potentially shippable code to a point where they are actually useable.

Myth#3 - DevOps is incompatible with ITIL

ITIL, for those who are not aware of it, is a library of practices aimed at codifying the practices and processes in the IT Operations (Ops). DevOps practices can be made compatible with ITIL. For shorter lead times and higher deployment frequencies many parts of ITIL need to be automated. Also, ITIL disciplines like service design, incident and problem management are relevant as DevOps requires faster detection and recovery

Myth#4 - Devops is incompatible with Information Security and Compliance

The absence of traditional controls may incur the disapproval of many infosec and compliance pros. The info sec and compliance actions are integrated into every stage of the software development lifecycle rather than being performed at the end of the project

Myth#5 - DevOps means eliminating IT Ops or NoOps

DevOps is not the complete elimination of the IT Ops function. This is not the case at all for most of the times. It remains as important as ever only its nature or the way of doing it changes. The collaboration with Ops begins far earlier in the software dev lifecyle and goes beyond code deployment. The Ops function helps in creating APIs and self-serviced platforms that: create environments test and deploy code monitor and display prod telemetry etc.. instead of doing manual work in response to work tickets So in effect, Ops (also QA and InfoSec) becomes more like Development engaged in creating a product which is the platform that is used by developers to safely, quicky and securely test, deploy and run their services in prod.

Myth#6 - DevOps is just Infra as Code or Automation

While many of the DevOps practices need automation, the DevOps way also needs culture and a model that allows for shared goals to be achieved throughout the IT value stream.

Myth#7 - DevOps is only for OpenSource software

DevOps outcomes can be achieved independent of the technology being used.