Gratuit avec l’offre d'essai
Site Reliability Engineering
- How Google Runs Production Systems
- Lu par : Liz Porter
- Durée : 20 h et 8 min
Échec de l’élimination de la liste d'envies.
Impossible de suivre le podcast
Impossible de ne plus suivre le podcast
Acheter pour 44,88 €
Vous êtes membre Amazon Prime ?Bénéficiez automatiquement de 2 livres audio offerts.
Bonne écoute !
Newly adapted for audiobook listeners.
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
PLEASE NOTE: When you purchase this title, the accompanying PDF will be available in your Audible Library along with the audio.
Ce que les auditeurs disent de Site Reliability EngineeringMoyenne des évaluations utilisateurs. Seuls les utilisateurs ayant écouté le titre peuvent laisser une évaluation.
Commentaires - Veuillez sélectionner les onglets ci-dessous pour changer la provenance des commentaires.
- Andreas Andersen
I didn't like it.
Google has a lot of special Google-sauce to make their mono-repo work for them. And sorta assumes everyone has the special Google-sauce.
Therefore, I don't consider most of the organizational advice applicable without modification.
An SRE is really just an Ops person that can program and is encouraged to solve their problems with code and automation.
They first make on-call seem daunting, then says it's a privilege new hires has to earn.
They spend a whole chapter on cron jobs. And make it seem like something magic Google invented....
The narrator is really robotic, maybe the voice of Google translate? It also sounds weirdly nervous at times.
4 personnes ont trouvé cela utile