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)
20
Index
21
Packt

Jumping into the valley

Viktor Farcic: Does that mean companies should not jump into whatever is "today"? If you're not into virtualization, don't jump into containers. If you're not into cloud-native applications, don't think about deploying to cloud.

Mike Kail: I think you first have to ask yourself, "Why are we doing that, and why does that matter for our business?" You need to tie that to potential results versus it being the newest and coolest technology that's going to make you cooler than Facebook, because that won't happen.

As developers or DevOps cultural employees, we tend to become overly enamored of technology. Just look at how Kubernetes is so cool or how containers and clouds are so great. But you need to tie that back to why you are doing this. Why does it matter for the business, and what benefits is this application going to have from being cloud-native or container-native?

I'm a big pro-cloud, pro-software-defined person...