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

DevOps and SRE

Viktor Farcic: Let's explore how the Google SRE thing relates to DevOps then. How do you define an SRE?

Nirmal Mehta: A site reliability engineer is an IT operations engineer who supports development teams and production systems based on Google DevOps methodologies.

One of the big things to come out of the SRE philosophies is that there's a risk associated with the budget of how many hours the SRE team gives their project team for fixing whatever happens.

You can deploy as risky a piece of software as you want, but if you burn through that budget, that's on you. If you're providing a service that isn't as critical, you have a higher budget, and so you can take more risk. Or you could say, "You know what, I need to save that up for certain times of the year, or certain events, and balance that out."

This approach in Google's DevOps methodology removes the ability to skirt around the pain because it puts the pain at the front and center.

Resolving...