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)

Vendor lock-in, AWS, and keeping up with the DevOps world

Viktor Farcic: With the companies you work with, do they express concern about vendor lock-in, for example, when they go to Amazon?

Sean Hull: Yes, actually I think a number of years have passed since a lot of companies were locked in with Oracle, and so much time has passed that there's a new generation of folks that haven't been bitten by that. I sense that there's less fear right now around Amazon lock-in than maybe there should be. There are tools like Terraform that can plug into Google Cloud; it can talk to the IBM Cloud, Azure, and AWS, among others, so you can deploy resources in any of those clouds if you've built your infrastructure code in Terraform. Terraform is like a layer on top of CloudFormation that implements that stuff in a generic way.

Viktor Farcic: What's your take on container schedulers: Kubernetes, Mesos, Swarm, and so on?

Sean Hull: I haven't done much with Kubernetes and Docker...