Book Image

DevOps Paradox

By : Viktor Farcic
Book Image

DevOps Paradox

By: Viktor Farcic

Overview of this book

DevOps promises to break down silos, uniting organizations to deliver high quality output in a cross-functional way. In reality it often results in confusion and new silos: pockets of DevOps practitioners fight the status quo, senior decision-makers demand DevOps paint jobs without committing to true change. Even a clear definition of what DevOps is remains elusive. In DevOps Paradox, top DevOps consultants, industry leaders, and founders reveal their own approaches to all aspects of DevOps implementation and operation. Surround yourself with expert DevOps advisors. Viktor Farcic draws on experts from across the industry to discuss how to introduce DevOps to chaotic organizations, align incentives between teams, and make use of the latest tools and techniques. With each expert offering their own opinions on what DevOps is and how to make it work, you will be able to form your own informed view of the importance and value of DevOps as we enter a new decade. If you want to see how real DevOps experts address the challenges and resolve the paradoxes, this book is for you.
Table of Contents (21 chapters)

What is DevOps, and how is it used?

Ádám Sándor: I'm a Java developer turned cloud-native consultant currently working for Container Solutions, an Amsterdam-based consultancy company, where we help companies adapt to cloud-native technologies while exploring the best practices in DevOps.

I believe that DevOps is a way of developing software where you break down the barriers between the people who develop software and the people who run the software in production. Ideally, this would mean that a single team can be responsible for running their own software in production, which can improve the time it takes to fix problems. DevOps can also improve the design of software because developers get plenty of feedback—which allows them to design solutions in such a way that they will be able to run those solutions. I very much believe this is part of the "you build it, you run it" philosophy.

Viktor Farcic: But why would anyone want to do that?