OFFRE LISEUSES
Une liseuse achetée = une housse offerte* jusqu'au 21 juin
Essential SRE Way of Working. Essential SRE, #2
Par :Formats :
Disponible dans votre compte client Decitre ou Furet du Nord dès validation de votre commande. Le format ePub est :
- Compatible avec une lecture sur My Vivlio (smartphone, tablette, ordinateur)
- Compatible avec une lecture sur liseuses Vivlio
- Pour les liseuses autres que Vivlio, vous devez utiliser le logiciel Adobe Digital Edition. Non compatible avec la lecture sur les liseuses Kindle, Remarkable et Sony
, qui est-ce ?Notre partenaire de plateforme de lecture numérique où vous retrouverez l'ensemble de vos ebooks gratuitement
Pour en savoir plus sur nos ebooks, consultez notre aide en ligne ici
C'est si simple ! Lisez votre ebook avec l'app Vivlio sur votre tablette, mobile ou ordinateur :
- FormatePub
- ISBN8233065590
- EAN9798233065590
- Date de parution31/01/2026
- Protection num.pas de protection
- Infos supplémentairesepub
- ÉditeurLinda Balsamo
Résumé
Ever been personally attacked by an alert at 03:00?The kind that says "unusual, " "degraded, " or (my favourite) "flapping, " as if your production system is a distressed bird and not a dependency tower held together by good intentions and tribal knowledge from 2019?Then this book is for you. Essential SRE: Way of Working is a practical, opinionated field guide to Site Reliability Engineering-written from the messy middle of real operations, where incidents happen, roadmaps change, and humans behave like humans under pressure.
This is not a neutral "on the one hand." tour of reliability theory. It's the set of mechanisms that still hold up when the room is loud, the incident channel is flying, and someone says: "It's fine, it's only in production."Inside, you'll learn how to build reliability without burning people out:. SLIs that measure reality where users actually live (not where your dashboard looks pretty).. SLOs as an engineering contract-what you promise, and what you don't..
Error budgets as a civilised way to argue about risk (with less theatre and more math).. Monitoring vs alerting (dashboards are not pagers).. Paging only when users pay the price (noise is not a KPI).. Toil reduction, automation you can trust, and on-call without martyrdom.. Incident response, calm communication, postmortems that create learning (not blame).. Runbooks that work at 03:00, change management for engineers who hate it, and progressive delivery that fails in tiny pieces.
Plus: modern reality. You'll also get pragmatic chapters on AIOps and AI in SRE-alert tuning, incident triage, copilots for runbooks/ChatOps, AI-assisted postmortems, and how to govern AI so it helps instead of confidently hallucinating you into downtime. Who this is forSREs, DevOps engineers, platform engineers, tech leads, and engineering managers who want fewer heroics, fewer surprise pages, clearer decisions, and systems (and teams) that behave predictably under load.
Buy it if: you want actionable reliability practices with humour and zero patience for vague "best practices."Skip it if: you're looking for a polite book that never takes a stance. Welcome in. Bring coffee. Bring your strongest opinions. Then be prepared to replace a few with mechanisms that still work at 03:00
This is not a neutral "on the one hand." tour of reliability theory. It's the set of mechanisms that still hold up when the room is loud, the incident channel is flying, and someone says: "It's fine, it's only in production."Inside, you'll learn how to build reliability without burning people out:. SLIs that measure reality where users actually live (not where your dashboard looks pretty).. SLOs as an engineering contract-what you promise, and what you don't..
Error budgets as a civilised way to argue about risk (with less theatre and more math).. Monitoring vs alerting (dashboards are not pagers).. Paging only when users pay the price (noise is not a KPI).. Toil reduction, automation you can trust, and on-call without martyrdom.. Incident response, calm communication, postmortems that create learning (not blame).. Runbooks that work at 03:00, change management for engineers who hate it, and progressive delivery that fails in tiny pieces.
Plus: modern reality. You'll also get pragmatic chapters on AIOps and AI in SRE-alert tuning, incident triage, copilots for runbooks/ChatOps, AI-assisted postmortems, and how to govern AI so it helps instead of confidently hallucinating you into downtime. Who this is forSREs, DevOps engineers, platform engineers, tech leads, and engineering managers who want fewer heroics, fewer surprise pages, clearer decisions, and systems (and teams) that behave predictably under load.
Buy it if: you want actionable reliability practices with humour and zero patience for vague "best practices."Skip it if: you're looking for a polite book that never takes a stance. Welcome in. Bring coffee. Bring your strongest opinions. Then be prepared to replace a few with mechanisms that still work at 03:00
