按年被提到
20142015 · 4 次2026
开源书›编程语言·No.68

Stuff Goes Bad: Erlang in Anger

出事了:Erlang 实战排障
Fred Hebert

面向生产环境的 Erlang/BEAM 运维与排障手册,篇幅短而实用

免费阅读 ↗
被推荐 · 22 人首次 2014-09-17 · 最近 2025-03-15官方免费在线(版权保留,作者或出版社免费放出)
22不同的人
24活跃月份
12有推荐的月份
28讨论串

Fred Hebert 写的免费电子书,不讲语言入门,专讲线上 Erlang 系统出问题后怎么办:如何诊断内存、过载、进程和调度问题,如何使用追踪和 crash dump 分析,并介绍作者的 recon 工具。内容紧凑,更像一本运维手册。它和 Erlang 入门书互补,属于跑过真实系统后才会觉得有用的那类书。

HN 为什么推荐它

HN 上的人推荐它,是因为超出了 Erlang 入门,讲了真实生产系统的排障经验,常被推荐给 Erlang 和 Elixir 的开发者;也有新手觉得它对初学者偏难。

难度 4 / 5约 8 小时
适合谁

维护 Erlang 或 Elixir 线上系统的开发者

读之前最好知道
1Erlang/OTP 基础
2Unix 命令行

怎么读

由 Claude 根据这本书和 HN 上的说法整理,可能有错
  1. 1先学会 Erlang/OTP 基础,再读这本
  2. 2在一个玩具应用里试一遍书里的诊断工具
  3. 3出线上问题时,按章节当手册查
  4. 4配合 Learn You Some Erlang 等入门书使用

HN 书评

推荐在前,同类按时间 · 每本最多保留 20 条,统计用全部提及 · 作者本人贴的不算
推荐rdtsc · 2015-01

“Speaking of awesome, check out other stuff Fred Hebert wrote.”

推荐看作者 Fred Hebert 的其他作品
Awk in 20 Minutes原评论 ↗
推荐davidw · 2016-02

“I wish there were more things like this: Stuff Goes Bad”

希望有更多这类超越入门的实用资料
Études for Erlang原评论 ↗
推荐al_chemist · 2016-05

“If you want to debug Erlang program then Erlang/OTP already includes tools to help you do that: Stuff Goes Bad - 92 page manual that includes:”

指出 Erlang/OTP 自带调试工具,附上 92 页手册
Investigating Erlang by reading its system calls原评论 ↗
推荐rdtsc · 2017-07

“And btw, thank you for writing Stuff Goes Bad and (链接) !”

感谢作者写了这本书
How Discord Scaled Elixir to 5M Concurrent Users原评论 ↗
推荐_asummers · 2017-08

“Don't sleep on your Erlang literature: Learn You Some Erlang, Erlang in Anger, Design for Scalability with OTP.”

劝学 Elixir 的人别忽视 Erlang 文献,把它列入必读
Joy of Elixir原评论 ↗
推荐davidw · 2017-08

“This also has some more advanced topics:”

推荐它,涵盖更多进阶主题
Why Elixir (2014)原评论 ↗
看全部 20 条 →
推荐dixel · 2018-05

“On the critics of the areas of focus I'd recommend the work done by Fred Herbert”

推荐 Fred Hebert 的工作,谈大规模维护 Erlang 平台的坑
What Sucks About Erlang (2008)原评论 ↗
推荐rdtsc · 2019-03

“Overall I would say this book is a good start Stuff Goes Bad”

称它是不错的入门,涉及运维、tracing 和生产实践
Achieving 100k connections per second with Elixir原评论 ↗
推荐mmartinson · 2019-05

“This is great resource Stuff Goes Bad”

称它是运行 BEAM 系统的好资源
推荐di4na · 2020-04

“Hmm I would say try to read Erlang in Anger, test it in a toy app, that is not hard to get.”

建议读它,并在玩具应用里试一试
Debugging Distributed Systems原评论 ↗
推荐toast0 · 2020-05

“Erlang in Anger [1] might be the closest, it will at least show some of the gotchas you run into.”

称它可能最接近需求,至少能展示会遇到的坑
Optimising for Concurrency: Comparing the BEAM and JVM virtual machines原评论 ↗
推荐bitwalker · 2022-06

“his ebook Erlang In Anger is excellent as well”

称作者的电子书 Erlang in Anger 也很棒
The hunt for a cluster-killer Erlang bug (2021)原评论 ↗
推荐toast0 · 2023-03

“It's been a while since I read it, but I think Stuff Goes Bad addresses some of this subject matter”

称它好像涉及这个话题,但已读过很久
Globally Distributed Elixir over Tailscale原评论 ↗
推荐di4na · 2023-11

“Have a quick look at”

建议看看,介绍 BEAM 内置的探测和 tracing 工具
Gleam: a type safe language on the Erlang VM原评论 ↗
推荐toast0 · 2024-10

“If you're debugging an Erlang system, you might want to look at Erlang in Anger.”

建议调试 Erlang 系统时看它
Ask HN: What is the best way to learn Erlang?原评论 ↗
引用qohen · 2015-02

“which describes dealing with issues in production, including memory issues”

指出它讲生产环境问题,包括内存问题
We [talko.com] Learned Us Some Erlang原评论 ↗
引用greenyoda · 2015-11

“Here's a link to the book's home page, where you can also find a link to the author's other free eBook”

给出书的主页,并提到作者另一本免费电子书
Erlang in Anger – Erlang ebook [pdf]原评论 ↗
引用alanning · 2016-08

“I know Erlang in Anger [1] is kind of written just for this but it feels pretty intense to me as a newbie.”

称它正是为此而写,但对新手偏吃力
Notes on Distributed Systems for Young Bloods (2013)原评论 ↗
引用a-saleh · 2020-05

“first look for a book like Stuff Goes Bad, read through it and consider, if this is the sort of stuff my colleagues will want/be capable to deal with.”

建议先找这类书读一遍,再判断同事能否应付
Ask HN: Who regrets choosing Elixir?原评论 ↗
引用grantjpowell · 2021-12

“I've worked in Erlang/Elixir for the past few years”

以多年 Erlang/Elixir 经验为背景提到它
The Deadlock Empire原评论 ↗