Take a photo of a barcode or cover
39 reviews for:
Site Reliability Engineering: How Google Runs Production Systems
Niall Richard Murphy, Chris Jones, Jennifer Petoff, Betsy Beyer
4.03 AVERAGE
39 reviews for:
Site Reliability Engineering: How Google Runs Production Systems
Niall Richard Murphy, Chris Jones, Jennifer Petoff, Betsy Beyer
4.03 AVERAGE
There’s interesting content for sure. But the writing isn’t engaging (the book is long so that becomes boring kinda fast) and some aspects of the google culture are real creepy (best example: “humans are imperfect machines” while talking about people management...)
challenging
informative
slow-paced
Although it is a series of essays, you can find a cohesive narrative throughout the book. Practices presented in this book is not to be treated as baseline standards, but goals to be achieved, moon shots if you like, but not unattainable ideals. This is a must read for anyone (not just *Ops people) that work as a software engineer.
There's a ton of great information here, and we refer to it regularly as we're trying to change the culture at work. I gave it a 4 instead of a 5 because it does suffer a little from the style – think collection of essays rather than a unified arc – but it's really worth reading even if it requires some care to transfer to more usual environments.
A useful checklist for production engineering is tarnished by the undercurrent of marketing/recruiting. Still deserves its place on the shelf if you deliver software for a living
There are some good ideas here as well as some fairly esoteric ones. For me, much of the value comes from the appendices: the checklists and templates.
you should read the first handful of chapters at least. error budgets and throughput- vs. latency-optimized systems are good stuff.
however, parts of this book are written in the kind of overly academic, self-satisfied language of silicon valley at its smuggest. i couldn't deal with it. i stopped reading very early.
however, parts of this book are written in the kind of overly academic, self-satisfied language of silicon valley at its smuggest. i couldn't deal with it. i stopped reading very early.
It's a dense resource, full of information related to the wide range of operations undertaken by Site Reliability Engineers. There are multiple targets, from practitioners to managers, with valuable information there for all. The book can be least effective when it describes Google-specific technology that supports operational goals. Ditto for the moments when the book veers too far into the theoretical and fails to provide concrete, actionable examples.
Because it's so dense, it really does require multiple, targeted reads to extract the most value.
It's the only guide of its type, currently, and to that end, the best :)
Because it's so dense, it really does require multiple, targeted reads to extract the most value.
It's the only guide of its type, currently, and to that end, the best :)
I've only skimmed it and read a few sections in depth as they felt relevant to the work I was doing. It's a mammoth book and very dry reading, more of a reference tome to keep handy on the shelves and consult from time to time.