0%

Book Description

DevOps and Site Reliability Engineering (SRE) have emerged in recent years as solutions for managing operations in IT and software development. Is one method better than the other? Will one of them eventually win out? This article explains why these two disciplines—in both practice and philosophy—are much more alike than you may think.

Humans have been thinking about better ways to operate things for millennia, but despite all of this effort and thought, running enterprise software operations well remains elusive for many organizations. In this article, IT operations experts provide the key tenets of DevOps and SRE, compare and contrast the two, and explain the incentives necessary to successfully adopt either approach.

Table of Contents

  1. How SRE Relates to DevOps
    1. Background on DevOps
      1. No More Silos
      2. Accidents Are Normal
      3. Change Should Be Gradual
      4. Tooling and Culture Are Interrelated
      5. Measurement Is Crucial
    2. Background on SRE
      1. Operations Is a Software Problem
      2. Manage by Service Level Objectives (SLOs)
      3. Work to Minimize Toil
      4. Automate This Year’s Job Away
      5. Move Fast by Reducing the Cost of Failure
      6. Share Ownership with Developers
      7. Use the Same Tooling, Regardless of Function or Job Title
    3. Compare and Contrast
    4. Organizational Context and Fostering Successful Adoption
      1. Narrow, Rigid Incentives Narrow Your Success
      2. It’s Better to Fix It Yourself; Don’t Blame Someone Else
      3. Consider Reliability Work as a Specialized Role
      4. When Can Substitute for Whether
      5. Strive for Parity of Esteem: Career and Financial
    5. Conclusion
3.21.231.245