• Complain

Beyer Betsy - The site reliability workbook: practical ways to implement SRE

Here you can read online Beyer Betsy - The site reliability workbook: practical ways to implement SRE full text of the book (entire story) in english for free. Download pdf and epub, get meaning, cover and reviews about this ebook. City: Sebastopol;CA, year: 2018, publisher: OReilly Media, genre: Home and family. Description of the work, (preface) as well as reviews are available. Best literature library LitArk.com created for fans of good reading and offers a wide selection of genres:

Romance novel Science fiction Adventure Detective Science History Home and family Prose Art Politics Computer Non-fiction Religion Business Children Humor

Choose a favorite category and find really read worthwhile books. Enjoy immersion in the world of imagination, feel the emotions of the characters or learn something new for yourself, make an fascinating discovery.

Beyer Betsy The site reliability workbook: practical ways to implement SRE

The site reliability workbook: practical ways to implement SRE: summary, description and annotation

We offer to read an annotation, description, summary or preface (depends on what the author of the book "The site reliability workbook: practical ways to implement SRE" wrote himself). If you haven't found the necessary information about the book — write in the comments, we will try to find it.

How SRE relates to DevOps -- Part 1. Foundations. Implementing SLOs -- SLO engineering case studies -- Monitoring -- Alerting on SLOs -- Eliminating toil -- Simplicity -- Part 2. Practices. On-call -- Incident response -- Postmortem culture : learning from failure -- Managing load -- Introducing non-abstract large system design -- Data processing pipelines -- Configuration design and best practices -- Configuration specifics -- Canarying releases -- Part 3. Processes. Identifying and recovering from overload -- SRE engagement model -- SRE : reaching beyond your walls -- SRE team lifecycles -- Organizational change management in SRE -- Example SLO document -- Example error budget policy -- Results of postmortem analysis.

Beyer Betsy: author's other books


Who wrote The site reliability workbook: practical ways to implement SRE? Find out the surname, the name of the author of the book and a list of all author's works by series.

The site reliability workbook: practical ways to implement SRE — read online for free the complete book (whole text) full work

Below is the text of the book, divided by pages. System saving the place of the last page read, allows you to conveniently read the book "The site reliability workbook: practical ways to implement SRE" online for free, without having to search again every time where you left off. Put a bookmark, and you can go to the page where you finished reading at any time.

Light

Font size:

Reset

Interval:

Bookmark:

Make
Praise for The Site Reliability Workbook

This new workbook will help people to take the sometimes theoretical and abstract concepts covered in Site Reliability Engineering out of the special context of the Googleplex and see how the same concepts work in other organizations. Im especially excited to see more detail in the analysis of toil, how to apply SRE principles to data pipelines, and the case study reports discussing practical service level management.

Kurt Andersen, Site Reliability Engineer, LinkedIn

This practical hands-on guide to implementing SRE is valuable for engineers at companies of all sizes. Its excellent to see this workbook being shared so that we can all move forward and build more reliable systems together. I was impressed with the level of detail shared; you can pick this book up and get started implementing SRE practices today .

Tammy Btow, Principal SRE, Gremlin

A timely reminder, from the team that made SRE a required practice for everyone operating at scale, that reliability is created by people. This book is full of practical examples of how to optimize for reliability by focusing on the interactions between users and engineers and between technology and tools, without losing sight of feature velocity. The result is a compelling, interesting, and thought-provoking companion to Site Reliability Engineering.

Casey Rosenthal, CTO, Backplane.io

Googles first book explained the what and why of SRE. This book shows you how to implement SRE at any company, startup or giant. Great work by the editorial team.

Jonah Horowitz, SRE at Stripe

In 2016, Google dropped Site Reliability Engineering on the operations world, and the operations world was never the same. For the first time people had access to over 500 pages of distilled information on what Google does to run its planet-wide infrastructure. Most people liked the book, a handful didnt, but nobody ignored it. It became a seminal work and an important touchstone for how people thought about SRE (especially the Google implementation of it) from that point on. But it was missing something.

Now in 2018, Google returns to fill in a crucial piece of the puzzle: in their first volume they described what they do, but that didnt help those who couldnt see themselves in Googles story. This book aims to demonstrate how Google does SRE and how you can do it, too .

David N. Blank-Edelman, editor of Seeking SRE: Conversations about Running Production Systems at Scale
and cofounder of the global set of SREcon conferences

The Site Reliability Workbook

edited by Betsy Beyer , Niall Richard Murphy , David K. Rensin , Kent Kawahara , and Stephen Thorne

Copyright 2018 Google LLC. All rights reserved.

Printed in the United States of America.

Published by OReilly Media, Inc. , 1005 Gravenstein Highway North, Sebastopol, CA 95472.

OReilly books may be purchased for educational, business, or sales promotional use. Online editions are also available for most titles (http://oreilly.com/safari). For more information, contact our corporate/institutional sales department: 800-998-9938 or corporate@oreilly.com .

Acquisitions Editor: Nikki McDonald

Indexer: Ellen Troutman-Zaig

Developmental Editor: Virginia Wilson

Interior Designer: David Futato

Production Editor: Kristen Brown

Cover Designer: Karen Montgomery

Copyeditor: Rachel Monaghan

Illustrator: Rebecca Demarest

Proofreader: Kim Cofer

  • August 2018: First Edition
Revision History for the First Edition
  • 2018-06-08: First Release
  • 2018-06-22: Second Release

See http://oreilly.com/catalog/errata.csp?isbn=9781492029502 for release details.

This work is part of a collaboration between OReilly and Google. See our statement of editorial independence.

The OReilly logo is a registered trademark of OReilly Media, Inc. The Site Reliability Workbook, the cover image, and related trade dress are trademarks of OReilly Media, Inc.

The views expressed in this work are those of the authors, and do not represent the publishers views. While the publisher and the authors have used good faith efforts to ensure that the information and instructions contained in this work are accurate, the publisher and the authors disclaim all responsibility for errors or omissions, including without limitation responsibility for damages resulting from the use of or reliance on this work. Use of the information and instructions contained in this work is at your own risk. If any code samples or other technology this work contains or describes is subject to open source licenses or the intellectual property rights of others, it is your responsibility to ensure that your use thereof complies with such licenses and/or rights.

978-1-492-02950-2

[LSCH]

Foreword I

Mark Burgess

Having introduced the first SRE book for OReilly, I am honored to be invited back for the sequel. In this book, the writing team is leaving the history of the first book to speak for itself and reaching out to a broader audience, offering direct experiences, case studies, and informal guidance. The broad themes will be familiar to anyone in IT, perhaps relabeled and reprioritized, and with a modern sense of business awareness. In place of technical descriptions, here we have user-facing services and their promises or objectives. We see human-computer systems originate from within the evolving business, intrinsic to its purpose, rather than as foreign meteorites impacting an unsuspecting and pristine infrastructure. Cooperation of all human-computer parts is the focus. Indeed, the book might be summarized as follows:

  • Commit to clear promises that set service objectives, expectations, and levels.
  • Assess those promises continuously, with metrics and budgetary limits.
  • React quickly to keep and repair promises, be on-call, and guard autonomy to avoid new gatekeepers.

Keeping promises reliably (to all stakeholders) depends on the stability of all their dependencies, of intent, and of the lives of the people involved (e.g., see Thinking in Promises). Remarkably, the human aspects of human-computer systems only grow alongside the perceived menace of scale: it turns out that automation doesnt eliminate humans, after all; rather, it challenges us to reassert human needs across all scales, from the genesis of an individual idea to the massive deployments on behalf of a global user base.

Teaching these lessons is a service challenge in its own rightand, like any service, hard-won knowledge is an iterative process. We make these lessons our own by questioning, trying, failing, rehearsing, and perfecting them. Theres a wealth of material to ponder and adapt in the book, so lets go.

Foreword II

Andrew Clay Shafer

When I found out people were working on a second SRE book, I reached out and asked if I could write a few words. The principles from the first SRE book align so well with what I always imagined DevOps to be, and the practices are insightful, even when they arent 100% applicable outside of Google. After reading the principles from the first SRE book for the first timeembracing risk (Chapter 3), service level objectives (Chapter 4), and eliminating toil (Chapter 5)I wanted to shout that message from the rooftops. Embracing risk resonated so much because I had used similar language many times to help traditional organizations motivate change. Chapter 6 was always an implicit DevOps goal, both to allow humans more time for creative higher-order work and to allow them to be more human. But I really fell in love with service level objectives. I love that the language and the process create a dispassionate contract between operational considerations and delivering new functionality. The SRE, SWE (software engineer), and business all agree that the service has to be up to be valuable, and the SRE solution quantifies objectives to drive actions and priorities. The solutionmake the service level a target, and when you are below the target prioritize reliability over featureseliminates a classic conflict between operations and developers. This is a simple and elegant reframing that solves problems by not having them. I give these three chapters as a homework assignment to almost everyone Ive met since. They are that good. Everyone should know. Tell all your friends. Ive told all mine.

Next page
Light

Font size:

Reset

Interval:

Bookmark:

Make

Similar books «The site reliability workbook: practical ways to implement SRE»

Look at similar books to The site reliability workbook: practical ways to implement SRE. We have selected literature similar in name and meaning in the hope of providing readers with more options to find new, interesting, not yet read works.


Reviews about «The site reliability workbook: practical ways to implement SRE»

Discussion, reviews of the book The site reliability workbook: practical ways to implement SRE and just readers' own opinions. Leave your comments, write what you think about the work, its meaning or the main characters. Specify what exactly you liked and what you didn't like, and why you think so.