Site Reliability Engineering pdf epub mobi txt 電子書 下載2025
Betsy Beyer
Betsy Beyer is a Technical Writer for Google in New York City specializing in Site Reliability Engineering. She has previously written documentation for Google’s Data Center and Hardware Operations Teams in Mountain View and across its globally distributed datacenters. Before moving to New York, Betsy was a lecturer on technical writing at Stanford University. En route to her current career, Betsy studied International Relations and English Literature, and holds degrees from Stanford and Tulane.
Chris Jones
Chris Jones is a Site Reliability Engineer for Google App Engine, a cloud platform-as-a-service product serving over 28 billion requests per day. Based in San Francisco, he has previously been responsible for the care and feeding of Google’s advertising statistics, data warehousing, and customer support systems. In other lives, Chris has worked in academic IT, analyzed data for political campaigns, and engaged in some light BSD kernel hacking, picking up degrees in Computer Engineering, Economics, and Technology Policy along the way. He’s also a licensed professional engineer.
Jennifer Petoff
Jennifer Petoff is a Program Manager for Google’s Site Reliability Engineering team and based in Dublin, Ireland. She has managed large global projects across wide-ranging domains including scientific research, engineering, human resources, and advertising operations. Jennifer joined Google after spending eight years in the chemical industry. She holds a PhD in Chemistry from Stanford University and a BS in Chemistry and a BA in Psychology from the University of Rochester.
Niall Richard Murphy
Niall Murphy leads the Ads Site Reliability Engineering team at Google Ireland. He has been involved in the Internet industry for about 20 years, and is currently chairperson of INEX, Ireland’s peering hub. He is the author or coauthor of a number of technical papers and/or books, including "IPv6 Network Administration" for O’Reilly, and a number of RFCs. He is currently cowriting a history of the Internet in Ireland, and is the holder of degrees in Computer Science, Mathematics, and Poetry Studies, which is surely some kind of mistake. He lives in Dublin with his wife and two sons.
- 運維
- SRE
- 計算機
- 服務器
- 分布式
- 架構
- 管理
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.
具體描述
讀後感
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 t...
評分注: 我不是做SRE的，我甚至都不是工程师（我算PM）, 但这本书中有个时间分配的方法很有意思，所以写一下 一、 紧急事件、工单永远处理不完怎么办？ 理想很丰满，现实很骨感 在大型科技公司工作，你以为能调用各种资源，为百万级用户来带价值，但实际却发现，因为稳定性、legacy...
評分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 t...
評分注: 我不是做SRE的，我甚至都不是工程师（我算PM）, 但这本书中有个时间分配的方法很有意思，所以写一下 一、 紧急事件、工单永远处理不完怎么办？ 理想很丰满，现实很骨感 在大型科技公司工作，你以为能调用各种资源，为百万级用户来带价值，但实际却发现，因为稳定性、legacy...
評分原文来自：http://blog.csdn.net/xindoo/article/details/52723114 《SRE》这本书英文版已面世半年后，中文版终于面世。从4月、5月的时候，我就一直在尝试看英文版，由于自己英文水平有限，阅读进度和深度实在有限，看到中文版，对很多章节的内容才算是有了较深入的理解，一句...
用戶評價
對我（非技術）更多是一本管理書, 尤其是對於high-stake如金融這類行業: (1) 怎麼解決新功能與穩定之間的衝突? -> 設定error budget + gradual rollout; (2) 緊急事件、工單永遠處理不完怎麼辦？-> 設定50% toil上限, 超過瞭招人或者讓産品團隊自己處理. 這樣纔有機會去做長期、自動化的改進. 這個方法對於運營類工作應該也類似, 設定時間上限, 一定設定時間去做抽象、自動化改造、總結
评分生詞太多。細緻的的看瞭下開頭和結尾章節。中間偏技術的章節 生詞多 沒耐心看瞭。
评分大概是最近一年來看的最吃力的一本書，幾乎隻能來迴挑著看，相當一部分topic都不是很有感覺，有經曆過的部分倒還好。整體上更應該作為文集掛在博客上而不是編纂齣書，每章節的內容大多都是互相彼此獨立，換個作者啥風格視角都變瞭，前後銜接不上。內容上還是以講述“我們如何做”為主，完全不考慮讀者的經驗背景。 最後隻能說一句，Google牛逼，Google的工程師真屌，處理突發事故還能到點下班，丟給另外一個半球的同事繼續handle，大部分碼農上哪去找另外一個半球的同事。。
评分撿瞭幾章名字感興趣的看瞭以後，主要是borgmon, load balancing和distributed consensus，對這本書是相當失望。最大的問題是，這本書很難讓人跟上思路並且開始思考，很多地方都在堆概念堆步驟，於是後果就是，隻有你在真正開發和運維這一塊的時候，你纔有可能藉鑒到一點東西，而另一個問題是，這本書對每一塊東西又沒有具體把整個思想的前因後果講清楚，很難把類似的概念對應到自己的産品上。在亞麻，創業公司，微軟都做過很多類似的工作，有可能是因為已有的cloud技術已經把這些運維的難點覆蓋的差不多瞭，並沒有覺得這本書有太多收獲。
评分最大的感覺：就像內功心法，能領會的人一般已有套路，沒套路的人也難get全心法。
相關圖書
本站所有內容均為互聯網搜索引擎提供的公開搜索信息，本站不存儲任何數據與內容，任何內容與數據均與本站無關，如有需要請聯繫相關搜索引擎包括但不限於百度，google,bing,sogou 等
© 2025 qciss.net All Rights Reserved. 小哈圖書下載中心 版权所有