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 big DevOps killer

But if you look at Kubernetes and what you're doing with it, it really doesn't make any sense to have a hypervisor on that. Because to the Java Virtual Machine (JVM), which is basically a virtualization layer between an operating system and the application, you're running it in a container. The argument can be made that it's like a virtual separation. It's not virtualization, but you know what I mean. Then, to have another layer of virtualization under that results in you taking your stuff pretty far from that CPU and memory.

Viktor Farcic: That may be true, but then how about serverless? Is that the next thing?

Wian Vos: I think serverless is the big DevOps killer.

Viktor Farcic: In what sense?

Wian Vos: I think it's basically the same as we had at the end of the 1990s, and before that in the 1970s. You as a developer do not want to be bothered with stuff that operations are doing, and because of that, we've have had six to seven years...