Amazon cover image
Image from Amazon.com
Image from Google Jackets

Site reliability engineering : how Google runs production systems / edited by Betsy Beyer, Chris Jones, Jennifer Petoff, and Niall Richard Murphy.

By: Contributor(s): Material type: TextTextPublication details: Sebastopol, CA: O'Reilly 2016Edition: First edition, April 2016Description: xxiv, 524 pages : illustrations ; 24 cmISBN:
  • 9781491929124
  • 149192912X
Subject(s): DDC classification:
  • 23 005.4 BEY
Contents:
Introduction. The production environment at Google, from the viewpoint of an SRE -- Principles. Embracing risk -- Service level objectives -- Eliminating toil -- Monitoring distributed systems -- The evolution of automation at Google -- Release engineering -- Simplicity -- Practices. Practical alerting from time-series data -- Being on-call -- Effective troubleshooting -- Emergency response -- Managing incidents -- Postmortem culture: learning from failure -- Tracking outages -- Testing for reliability -- Software engineering in SRE -- Load balancing at the frontend -- Load balancing in the datacenter -- Handling overload -- Addressing cascading failures -- Managing critical state: distributed consensus for reliability -- Distributed periodic scheduling with Cron --Data processing pipelines -- Date integrity: what you read is what your wrote -- Reliable product launches at scale -- Management. Accelerating SREs to on-call and beyond -- Dealing with interrupts -- Embedding an SRE to recover from operational overload -- Communication and collaboration in SRE -- The evolving SRE engagement model -- Conclusions. Lessons learned from other industries.
Summary: "The overwhelming majority of a software system's lifespan is spent in use, not in design or implementation. So, why does conventional wisdom insist that software engineers focus primarily on the design and development of large-scale computing systems? In this collection of essays and articles, key members of Google's Site Reliability Team explain how and why their commitment to the entire lifecycle has enabled the company to successfully build, deploy, monitor, and maintain some of the largest software systems in the world. You'll learn the principles and practices that enable Google engineers to make systems more scalable, reliable, and efficient - lessons directly applicable to your organization. This book is divided into four sections: Introduction - Learn what site reliability engineering is and why it differs from conventional IT industry practices; Principles - Examine the patterns, behaviors, and areas of concern that influence the work of a site reliability engineer (SRE); Practices - Understand the theory and practice of an SRE's day-to-day work: building and operating large distributed computing systems; Management - Explore Google's best practices for training, communication, and meetings that your organization can use."--Publisher's description.
Tags from this library: No tags from this library for this title. Log in to add tags.
Holdings
Item type Current library Collection Call number Status Date due Barcode
Books Books School of Theoretical Physics Library Books 005.4 BEY (Browse shelf(Opens below)) Available 11780

Includes bibliographical references (pages 501-512) and index.

Introduction. The production environment at Google, from the viewpoint of an SRE -- Principles. Embracing risk -- Service level objectives -- Eliminating toil -- Monitoring distributed systems -- The evolution of automation at Google -- Release engineering -- Simplicity -- Practices. Practical alerting from time-series data -- Being on-call -- Effective troubleshooting -- Emergency response -- Managing incidents -- Postmortem culture: learning from failure -- Tracking outages -- Testing for reliability -- Software engineering in SRE -- Load balancing at the frontend -- Load balancing in the datacenter -- Handling overload -- Addressing cascading failures -- Managing critical state: distributed consensus for reliability -- Distributed periodic scheduling with Cron --Data processing pipelines -- Date integrity: what you read is what your wrote -- Reliable product launches at scale -- Management. Accelerating SREs to on-call and beyond -- Dealing with interrupts -- Embedding an SRE to recover from operational overload -- Communication and collaboration in SRE -- The evolving SRE engagement model -- Conclusions. Lessons learned from other industries.

"The overwhelming majority of a software system's lifespan is spent in use, not in design or implementation. So, why does conventional wisdom insist that software engineers focus primarily on the design and development of large-scale computing systems? In this collection of essays and articles, key members of Google's Site Reliability Team explain how and why their commitment to the entire lifecycle has enabled the company to successfully build, deploy, monitor, and maintain some of the largest software systems in the world. You'll learn the principles and practices that enable Google engineers to make systems more scalable, reliable, and efficient - lessons directly applicable to your organization. This book is divided into four sections: Introduction - Learn what site reliability engineering is and why it differs from conventional IT industry practices; Principles - Examine the patterns, behaviors, and areas of concern that influence the work of a site reliability engineer (SRE); Practices - Understand the theory and practice of an SRE's day-to-day work: building and operating large distributed computing systems; Management - Explore Google's best practices for training, communication, and meetings that your organization can use."--Publisher's description.

There are no comments on this title.

to post a comment.