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)

DevOps departments

Viktor Farcic: What do you think about DevOps departments then? I'm seeing quite a lot of them today, especially in enterprises. When I take a closer look at these enterprises, I'm told they're going to form this DevOps department that will be in charge of doing DevOps for the whole company.

Chris Riley: Going back to that large media company I referenced earlier, that's what they do. They implement but they're not responsible for implementing organization-wise. They're more responsible for knowing both what the best practices and the best tools are. What they do implement organization-wise are things such as chatbots, integrations with AWS or whatever the cloud provider is, and things that truly are tools that you would use because what they're integrating with is global.

Everybody uses Slack, so they can create things for Slack. Everybody is using the same cloud, so they can create things for this cloud. That's where I think you...