Site Reliability Engineering

Site Reliability Engineering (SRE) is a discipline that incorporates aspects of software engineering and applies them to infrastructure and operations problems.[1] The main goals are to create scalable and highly reliable software systems. According to Ben Treynor, founder of Google's Site Reliability Team, SRE is "what happens when a software engineer is tasked with what used to be called operations."[2]

Roles

A Site Reliability Engineer (SRE) will spend up to 50% of their time doing "ops" related work such as issues, on-call, and manual intervention. Since the software system that an SRE oversees is expected to be highly automatic and self-healing, the SRE should spend the other 50% of their time on development tasks such as new features, scaling or automation. The ideal site reliability engineer candidate is either a software engineer with a good administration background or a highly skilled system administrator with knowledge of coding and automation[3].

DevOps vs SRE
Main article: DevOps

Coined around 2008, DevOps is a philosophy of cross-team empathy and business alignment. It's also been associated with a practice that encompasses automation of manual tasks, continuous integration and continuous delivery. SRE and DevOps share the same foundational principles. SRE is viewed by many (as cited in the Google SRE book) as a "specific implementation of DevOps with some idiosyncratic extensions." SREs, being developers themselves, will naturally bring solutions that help remove the barriers between development teams and operations teams.

DevOps defines 5 key pillars of success:

  1. Reduce organizational silos
  2. Accept failure as normal
  3. Implement gradual changes
  4. Leverage tooling and automation
  5. Measure everything

SRE satisfies the DevOps pillars as follows:[4]

  1. Reduce organizational silos
    • SRE shares ownership with developers to create shared responsibility[5]
    • SREs use the same tools that developers use, and vice versa
  2. Accept failure as normal
    • SREs embrace risk[6]
    • SRE quantifies failure and availability in a prescriptive manner using Service Level Indicators (SLIs) and Service Level Objectives (SLOs)[7]
    • SRE mandates blameless post mortems[8]
  3. Implement gradual changes
    • SRE encourages developers and product owners to move quickly by reducing the cost of failure[6]
  4. Leverage tooling and automation
    • SREs have a charter to automate menial tasks (called "toil") away[9]
  5. Measure everything
    • SRE defines prescriptive ways to measure values[10]
    • SRE fundamentally believes that systems operation is a software problem
gollark: <:transistor:786305136066691082> <:rust:786305136771072022>
gollark: IKR, right?
gollark: <@711227962401226793> Good news, I added my entire emoji library except :seaweed:.
gollark: https://tvtropes.org/pmwiki/pmwiki.php/Main/TakeAThirdOption
gollark: Something something third option?

See also

References
  1. What Does a Reliability Engineer Do?
  2. Are SRE the next data scientists?, TechCrunch, Mar 2, 2016, Donald Fischer
  3. Jones, Chris; Underwood, Todd; Nukala, Shylaja (June 2015). "Hiring Site Reliability Engineers" (PDF). ;login:. Vol. 40 no. 3. pp. 35–39.CS1 maint: extra punctuation (link)
  4. Google Cloud Platform (1 March 2018). "What's the Difference Between DevOps and SRE? (class SRE implements DevOps)". pp. 35–39 – via YouTube.
  5. "Google - Site Reliability Engineering". landing.google.com.
  6. "Google - Site Reliability Engineering". landing.google.com.
  7. "Google - Site Reliability Engineering". landing.google.com.
  8. "Google - Site Reliability Engineering". landing.google.com.
  9. "Google - Site Reliability Engineering". landing.google.com.
  10. "Google - Site Reliability Engineering". landing.google.com.
General
  • Site Reliability Engineering: How Google Runs Production Systems, O'Reilly Media, April 2016, Betsy Beyer, Chris Jones, Jennifer Petoff, Niall Richard Murphy, ISBN 978-1-491-92912-4
  • The Practice of Cloud System Administration: Designing and Operating Large Distributed Systems, Volume 2, Thomas Limoncelli, ISBN 032194318X
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.