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

Monoliths and microservices

Viktor Farcic: You mentioned monoliths and microservices. Can you explain why they've only become popular now? I mean, obviously, microservices have existed for a number of years. Is that because our needs changed or the tools that we have access to changed? It's not that that concept didn't exist for a long time, but everybody only started talking about them recently.

James Turnbull: When I first started out in the industry, there was a concept called service-oriented architecture. Primarily, it was a way to break services into individual fault domains that allowed them to scale, manage, and interact on their own. The definition of service was pretty broad. It generally didn't resemble a microservice.

But I think a couple of things have happened, namely that virtualization, the cloud, and containers have enabled microservices architecture. They're very easy tools to allow someone to build those services.

I think the reason those services...