SRE：Google 运维解密

Hacker News 上怎么说

• web007 · 2016 年

  算是有那么点吧，但大部分不是。去读读 Beyer 等人写的《Site Reliability Engineering》。那是关于 on-call 应该如何运作的最清晰描述，也是怎样从现状走到目标状态且不至于把人搞到 burnout 的途径。On-call 几乎总是必要的，但应该被当成……

  Sort of yes, but mostly no. Go read "Site Reliability Engineering" by Beyer et al. That's the clearest description for how on-call should work, and the way to get from Point A to Point B without burning anyone out. On-call is almost always necessaey, but should be thought…

• SwellJoe · 2017 年

  ……招聘策略；优秀的人通常都会参加技术大会，当他们听说有这么一家由聪明人组成、演讲又精彩的神仙公司时，也会想去那里工作。出书也是同理。读《Site Reliability Engineering》会让我很想去 Google 工作（尽管我很清楚自己其实根本不想去 Google）。优秀的人会吸引更多优秀的人，而且优秀的人充满热情，在工作之外也会做一些很酷的事情。……

  …recruiting tactic; often, good people are at conferences, and when they hear about a great company to work for with smart people who give good talks, they want to work there, too. Books are similar. Reading Site Reliability Engineering makes me want to work at Google (even though I know I really don't want to work at Google). Good people bring in more good people, and good people are enthusiastic and do cool things outside of work.…

• eatonphil · 2022 年

  针对后端开发者的系统和设计类推荐：1. High Performance Browser Networking 2. Designing Data-Intensive Applications 3. Site Reliability Engineering: How Google Runs Production Services 4. Effective Python: 90 Specific Ways to Write Better Python。我在这里写了更详细的介绍：https://notes.eatonphil.com/books-developers-should-read.htm....…

  Focused on systems and design for backend devs: 1. High Performance Browser Networking 2. Designing Data-Intensive Applications 3. Site Reliability Engineering: How Google Runs Production Services 4. Effective Python: 90 Specific Ways to Write Better Python I wrote in a bit more detail here: https://notes.eatonphil.com/books-developers-should-read.htm....…

• samuell · 2022 年

  在我看来，这些书值得好好精读消化：软件工程实践：- Designing Data-Intensive Applications - Site Reliability Engineering - Software Engineering at Google - Designing Event-Driven Systems - The Data-Centric Revolution - Code Complete - Data Management at Scale 个人成长：- So Good They Can't Ignore You - Deep Work……

  These are the books that IMO felt worth really carefully digesting: Software engineering practices: - Designing Data-Intensive Applications - Site Reliability Engineering - Software Engineering at Google - Designing Event-Driven Systems - The Data-Centric Revolution - Code Complete - Data Management at Scale Self-help: - So Good They Can't Ignore You - Deep Work…

• belfalas · 2023 年

  ……Action - Raoul-Gabriel Urma * Java Concurrency in Practice - Brian Goetz * Grokking Algorithms - Aditya Y. Bhargava 架构类：* Righting Software - Juval Lowy * Release It! - Michael Nygard * Site Reliability Engineering - Beyer, et al.（“SRE 神书”）* Domain Driven Design - Eric Evans * Introduction to Permaculture - Bill Mollison and Mia Slay * Fun with a Pencil - Andrew Loomis 设计类：* Edward……写的所有书

  …Action - Raoul-Gabriel Urma * Java Concurrency in Practice - Brian Goetz * Grokking Algorithms - Aditya Y. Bhargava Architecture: * Righting Software - Juval Lowy * Release It! - Michael Nygard * Site Reliability Engineering - Beyer, et al. ("The SRE Book”) * Domain Driven Design - Eric Evans * Introduction to Permaculture - Bill Mollison and Mia Slay * Fun with a Pencil - Andrew Loomis Design: * All books by Edward…

• jsmthrowaway · 2017 年

  ……Docker 提供的能力。这使得搞清楚‘怎么做到’成了你的职责，而不是去讨论‘要不要做’。不对，不对，完全不对。我完整引用了这整段话，是因为它错得彻彻底底。去读读 Google 刚出版的《Site Reliability Engineering》，看看另一种视角吧。Google 的 SRE 架构明确且坚定地被赋予了向研发工程团队 push back 的权力。毫无例外。“不行”绝对是一个完全正当的……

  …Docker offers. That makes it your job to figure out how that happens, not if it happens. Nope, nope, nope, nope. I quoted this entire paragraph at length because it's all just completely wrong. Read Site Reliability Engineering that Google just published for an alternative perspective. SRE at Google is specifically and vocally organized to have authority to push back on engineering. Without exception. "No" is absolutely a valid…

正在加载完整评论……