Site Reliability Engineering: How Google Runs Production Systems
Product ID: 52888357
Buy anything from 5,000+ international stores. One checkout price. No surprise fees. Join 2M+ shoppers on Desertcart.
Desertcart purchases this item on your behalf and handles shipping, customs, and support to Hong Kong.
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 Review: The book every infrastructure engineer and DevOps person should read - If you are new to infrastructure engineering this book will inform you as to an approach and model to use as you start down this road. If you are an experienced engineer then you will see a lot of truth in what is written here. It may change you viewpoint or solidify an existing one, whatever the case this book is an essential reference and an honest account with a huge amount of wisdom. Review: Great! - New, arrived in great condition and protected
| Best Sellers Rank | 196,360 in Books ( See Top 100 in Books ) 36 in Computer Databases (Books) 63 in UNIX & Linux 402 in Software Design & Development |
| Customer Reviews | 4.6 out of 5 stars 1,199 Reviews |
J**S
The book every infrastructure engineer and DevOps person should read
If you are new to infrastructure engineering this book will inform you as to an approach and model to use as you start down this road. If you are an experienced engineer then you will see a lot of truth in what is written here. It may change you viewpoint or solidify an existing one, whatever the case this book is an essential reference and an honest account with a huge amount of wisdom.
N**E
Great!
New, arrived in great condition and protected
A**D
Four Stars
Good Value product and quick delivery - Thank you !
A**N
Interesting reading
Good book with some examples about how Google engineers are running their huge infrastructure. It offers some guidelines and suggestions from people/team management to automation and good software engineering practices.
K**C
Interesting read, good level of detail.
Good insight in to the details of how Google does it, and how to think beyond the DevOps mindset
P**D
great print quality
pretty good print quality. I know it's a free book but nothing beats having a copy in your hand.
D**T
Why does this have such great reviews?
It's hard to tell who this book is aimed at. If you are a non-technical manager, a lot of the content is probably too technical. If you are a fairly technical operations/support person, you'll likely come away from it thinking "yeah that's all well and good but how am I supposed to get my entire organisation into this way of thinking?" The book tells a nice story but offers little practical advice for anyone embarking on a SRE or DevOps journey, or for anyone looking to bring it into their organisation.
J**V
Excellent trove of knowledge
Excellent trove of knowledge, condensing over a decade of Google's "let's try this... hmm... okay, how about like this... whoops, okay, new plan... well that seems to do it" learning into one fat tome. Essential for anyone concerned with more than a couple of racks of hardware.
N**S
Must read for the serious DevOps engineer
Just the first chapter alone lists a number of concrete issues that anyone who has any experience with operations at all will both recognise, and the recommendations this book makes just make sense. Actually, not only people with DevOps experience should be reading this, there is a lot in here that their managers could certainly profit from, in every sense of the word. Key words: - Error budget - Toil / development ballance (and the 50% time rule) - The impossibility of never having a failure. I'm still working my way through the book, but every new chapter has new insights that really help to put our complex job into perspective, and offer concrete ways of making our work better.
G**I
Deep info
What to know about an Engineer - read this book - it's Deep
C**F
Interesting and useful
Of course, I have not the same infrastructure like Google but many problems are the same. This book is very interesting because shows different tips & tricks to resolve and manage communication problems between departments and of course reliability problems. I suggest it to every IT professional, ITIL experts, DevOps wannabe and of course CTO.
Ó**Z
Excelente libro
Libro excelente que da muchos puntos de vista de como formar un equipo de trabajo y cómo afrontar los problemas. También recorre todos los procesos de una empresa: presupuestos, monitorización, sla, puesta marcha servicio, mantenimiento de un servicio... En este libro se ve que la cultura de Google es "blameless" y que no hay una línea entre devs y ops, existe el concepto de SRE que podría decirse que es parecido al actual de devops, aunque con más funciones. Libro que debería leer toda persona que trabaja en IT y también a toda la
D**L
A must read book
A must read book
Trustpilot
1 month ago
3 weeks ago