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

The evolution of containers

Julian Simpson: I think containers have changed a lot because you have this constant migration of value up the stack.

Viktor Farcic: What do you mean by that?

Julian Simpson: We used to keep this business logic and store procedures in the database, but it moved into code running above the database. I think we're a long way from seeing where the container thing is going to end up, but it seems like that's the biggest change. No one's interested in the host OS anymore.

Viktor Farcic: You mean as if it's not the lowest denominator anymore?

Julian Simpson: Yeah, I think in some ways it's incredibly helpful that whether you're looking at containers or platform as a service, people can deliver code using them. I haven't been that interested in the gory details of container runtimes; I'm just happy that if I want to roll out something, I can deploy it on ECS, or whatever container runtime as a service exists.

Viktor Farcic: I think...