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

What is DevOps?

Andy Clemenko: DevOps is a lifestyle. It's all about being able to adapt to new technologies, not only from a developer point of view, but also an operations point of view, while still being nimble. That's not to say DevOps is only that. There are a lot of other concepts built into it, which is why I call it a lifestyle. Beyond being able just to adapt, you've also got containers, twelve-factor apps, declarative infrastructure, and infrastructure as code. Yes, you've got all of these buzzwords around it, but at the end of the day, it's just a lifestyle. It's about being nimble, retooling, and moving forward.

Viktor Farcic: So, how does Andy Clemenko fit tools into that picture? Because, in today's field, I'm finding that every tool is a DevOps tool.

Andy Clemenko: To a certain extent, the tools almost don't matter, because you can hand a carpenter any hammer and they'll still be successful. Within DevOps, you give any DevOps...