BEAM Concurrency in Action
summary
BEAM runtime (Erlang VM) is used to run millions of BEAM processes that communicate by message passing via PIDs and mailboxes; long queries that take minutes or hours run in spawned processes so a websocket session stays responsive; a sports ingestion pipeline uses per‑match dynamic processes to limit GC and isolate failures; dispatch uses adaptive batching driven by a dispatcher demand loop to handle few dozen to a few hundred messages/sec; CI is implemented as a supervised process tree and supports graceful cancellation by sending an exit signal (or trapping exits).
AI-written summary · about
chapters (4)
related talks
51mThe Erlang VM or How I Started Loving Parallel Progamming
52mConcurrency Oriented Programming in a Modern World
37mCrashing BEAM applications
42mConcurrency Oriented Software
43mConcurrency Abstractions for Application Security
40mComparison and Commentary on "Application Operating System"
23mElixir GenServer: Understanding Elixir concurrency model
34mComparing the Actor model & CSP concurrency with Elixir & Clojure