![[Review] Site Reliability Engineering: How Google Runs Production Systems (Jennifer Petoff) Summarized.](https://episodes.castos.com/660078c6833215-59505987/images/2663041/c1a-085k3-8ddw0j5rtw5z-qdnsd0.jpg)
Show Notes
Site Reliability Engineering: How Google Runs Production Systems (Jennifer Petoff)
- Amazon USA Store: https://www.amazon.com/dp/149192912X?tag=9natree-20
- Amazon Worldwide Store: https://global.buys.trade/Site-Reliability-Engineering%3A-How-Google-Runs-Production-Systems-Jennifer-Petoff.html
- Apple Books: https://books.apple.com/us/audiobook/site-reliability-engineering-how-google-runs-production/id1573412970?itsct=books_box_link&itscg=30200&ls=1&at=1001l3bAw&ct=9natree
- eBay: https://www.ebay.com/sch/i.html?_nkw=Site+Reliability+Engineering+How+Google+Runs+Production+Systems+Jennifer+Petoff+&mkcid=1&mkrid=711-53200-19255-0&siteid=0&campid=5339060787&customid=9natree&toolid=10001&mkevt=1
- Read more: https://english.9natree.com/read/149192912X/
#SoftwareEngineeringforOperations #ServiceLevelObjectives #ErrorBudgets #ToilReduction #BlamelessPostmortems #SiteReliabilityEngineering
Site Reliability Engineering: How Google Runs Production Systems is a 2016 technical anthology edited by Betsy Beyer, Chris Jones, Jennifer Petoff, and Niall Richard Murphy. Often called the SRE book, it explains Google’s approach to operating large distributed services through software engineering rather than through a separate, largely manual operations function. Its subject is not a single product or a step by step tool manual. Instead, chapters by Google practitioners connect organizational design, service measurement, automation, on call work, incident response, capacity planning, monitoring, and change management. The book argues that production systems spend most of their lives being operated, so operational quality must be designed and engineered from the start. Its central purpose is to show how reliability can become measurable, negotiable, and improvable without freezing product development. Although examples reflect Google’s scale and internal environment, the framework has shaped the broader vocabulary of cloud operations and DevOps. Readers receive both a philosophy of responsibility for live services and practical criteria for deciding which operational work should be automated or redesigned.
- Amazon USA Store: https://www.amazon.com/dp/149192912X?tag=9natree-20
- Amazon Worldwide Store: https://global.buys.trade/Site-Reliability-Engineering%3A-How-Google-Runs-Production-Systems-Jennifer-Petoff.html
- Apple Books: https://books.apple.com/us/audiobook/site-reliability-engineering-how-google-runs-production/id1573412970?itsct=books_box_link&itscg=30200&ls=1&at=1001l3bAw&ct=9natree
- eBay: https://www.ebay.com/sch/i.html?_nkw=Site+Reliability+Engineering+How+Google+Runs+Production+Systems+Jennifer+Petoff+&mkcid=1&mkrid=711-53200-19255-0&siteid=0&campid=5339060787&customid=9natree&toolid=10001&mkevt=1
- Read more: https://english.9natree.com/read/149192912X/
#SoftwareEngineeringforOperations #ServiceLevelObjectives #ErrorBudgets #ToilReduction #BlamelessPostmortems #SiteReliabilityEngineering
Site Reliability Engineering: How Google Runs Production Systems is a 2016 technical anthology edited by Betsy Beyer, Chris Jones, Jennifer Petoff, and Niall Richard Murphy. Often called the SRE book, it explains Google’s approach to operating large distributed services through software engineering rather than through a separate, largely manual operations function. Its subject is not a single product or a step by step tool manual. Instead, chapters by Google practitioners connect organizational design, service measurement, automation, on call work, incident response, capacity planning, monitoring, and change management. The book argues that production systems spend most of their lives being operated, so operational quality must be designed and engineered from the start. Its central purpose is to show how reliability can become measurable, negotiable, and improvable without freezing product development. Although examples reflect Google’s scale and internal environment, the framework has shaped the broader vocabulary of cloud operations and DevOps. Readers receive both a philosophy of responsibility for live services and practical criteria for deciding which operational work should be automated or redesigned.
