Skip to content
0:00 / 0:00

#beam#erlang#robertvirding

Robert Virding - Hitchhiker's Tour of the BEAM

Erlang Solutions

18K subscribers • 48 videos on Hallway

YouTube
  • Recommended by 3 people: 1 on Lobsters and 2 in engineering communities.
  • A classic. People kept recommending it from 2016 to 2022.
  • Presented by Robert Virding, co-creator of Erlang

Intermediate. Assumes working knowledge.

16K views12 years ago3 recommendations

Systems programmingProgramming languagesElixir and ErlangConcurrency and parallelismOperating systems

Robert Virding takes viewers on an internal tour of the BEAM virtual machine, explaining how it handles concurrency and fault tolerance.

The BEAM is the standard Erlang implementation in use today. It was specially designed just to run Erlang. We will make a quick tour of the BEAM visiting the major sights to see what it looks like internally and how it functions. There will be no need of a towel on this short tour. Target audience: Developers and system architects who want to get a better understanding of how their applications will run.

Why it's here

3 people recommend this

What people say. Recommended as an essential guide to understanding how the BEAM virtual machine works internally, especially regarding concurrency.

tbonesteakson Lobsters • Recommends

Hitchhiker's Tour of the BEAM (2014)

u/perishabledavein r/elixir • Recommends

On “would elixir / phoenix be suitable for an api gateway?”

link to this video This should give you a good idea of how BEAM handles concurrency and should answer most of your questions.

u/akadmacgyverin r/elixir • Recommends

On “What makes Elixir stand out for backends?”

What you should look for is not language itself but BEAM aka. Erlang VM. >Lo√Øc Hogun (author of Cowboy, other projects) hits the nail on the head: For me Erlang/Elixir is first fault tolerant, then concurrent, then functional, yet for many people it seems to be the opposite order. I personally care very little about Erlang being functional (though I do care a great deal about immutability and pattern matching being the default behaviour, the rest not so much), and the concurrency is nice but only because it enables all the fault tolerance features of the language. I suggest you to really understand the principles of BEAM and dive into its architecture by…