Welcome to The BEAM DYK Pocketbook!
This book is a curated collection of my LinkedIn posts from the #BEAMDYK series, where I share insights, trivia, and fascinating details about the BEAM, the Erlang virtual machine, which was built in the 80's by Ericsson to automate telecom switches and now powers some of the world’s most robust, scalable, distributed, concurrent, and fault-tolerant systems, whether coded in Erlang, Elixir, or the newcomer Gleam.
This isn’t just a book for engineers or coding enthusiasts. It’s written with a broader audience in mind: entrepreneurs, business leaders, and tech-curious individuals who want to understand why the BEAM matters, how it adds value to business, and what makes it a unique value proposition for both businesses and engineers.
While most programming language runtimes are designed to execute code efficiently and as fast as possible, where system crashes are costly and often unavoidable within the capabilities of their runtimes, the BEAM is designed to keep systems running no matter what, embracing failure as a normal state. The design philosophy of the BEAM follows the principle of “let it crash," an approach that allows BEAM processes to fail and restart without impacting the overall system. This resilience is built in from the beginning and is one of the reasons why services built on the BEAM have industry-leading uptime and reliability.
For a more comprehensive and detailed tour of the BEAM, you will want to read The BEAM DYK Handbook, which dives into each DYK in this book and includes illustrations and diagrams to make concepts easier to understand.