Skip to content
Tech News
← Back to articles

Author details decade-long creation of The BEAM Book for Erlang/Elixir engineers

read original get The BEAM Book (Erlang VM internals) → more articles
GoKawiil Brief

A Klarna engineer recounts writing The BEAM Book over roughly thirteen years, starting from a four-line DocBook file in October 2012. The project survived a format switch to AsciiDoc, a troubled stint with O'Reilly's Atlas publishing system, cancelled contracts with both O'Reilly and Pragmatic Bookshelf, and a 2017 migration into a new repository containing over a million lines of text.

Why It Matters

GoKawiil's interpretation of the reporting above, not reported fact.

The account illustrates how niche technical documentation on low-level runtime internals like the BEAM virtual machine can take years to produce, often outlasting publisher relationships and tooling changes. For engineers running performance-sensitive systems such as payment processing, this kind of deep reference material could help diagnose rare latency issues that have outsized business consequences.

Key Takeaways
Worth a Look

The BEAM Book (Erlang VM internals) — If you're intrigued by the deep-dive into BEAM internals described in this article, this book is the definitive technical reference for understanding the Erlang virtual machine's scheduler, memory model, and concurrency guts. It's an essential read for engineers building high-reliability, low-latency systems like payment platforms.

See The BEAM Book (Erlang VM internals) on Amazon → Affiliate link — we may earn a commission on purchases, at no extra cost to you. Product picked by AI based on this article; it is not a tested recommendation.

Source: happihacking.com, 2026-11-09

Published there as: “Why I wrote the BEAM book (2025)”

Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.
Keep reading
atlas 49 briefs → klarna 4 briefs →