#Beam
13 notas · última:
Measuring memory consumption on the BEAM
Explains Benchee’s new feature for benchmarking memory usage of Elixir/Erlang functions, how it works on the BEAM, and its current limitations and requirements.
Adding Gleam to your Elixir project
Step‑by‑step guide to integrating a Gleam (rebar3) app into a Phoenix umbrella, wiring Mix to compile it, avoiding umbrella warnings, and calling Gleam from Elixir.
What's Inside a Reduction?
Examines how BEAM reductions are counted, showing that many non-reduction instructions and BIFs affect runtime, so reduction counts poorly track performance.
Building Distributed Systems in Elixir: Part 4 — Process Linking
The article explains how `spawn_link/1` connects two BEAM processes so an abnormal exit in one can terminate the other, and how `Process.flag(:trap_exit, true)` turns that exit into a message.
Building Distributed Systems in Elixir: Part 3 — Process Monitoring
Shows how BEAM process monitoring uses Process.monitor/1 to receive :DOWN messages when a worker stops or crashes, without polling, GenServer, or Supervisor.
Building Distributed Systems in Elixir: Part 1 - Building a Stateful Process in Elixir Without GenServer
The article shows how a counter can be built as a BEAM process with private state, message passing, and a recursive receive loop, then contrasts that core model with what GenServer adds.
Pesquisa Viva: Distributed Systems Patterns
General patterns for building distributed systems, one pattern at a time, using krishnadaspc's Elixir series built on raw BEAM primitives as the main thread.
A brief introduction to BEAM
This primer explains BEAM as the virtual machine that executes Erlang code, distinguishes it from ERTS, and shows how registers, calls, tuples, exceptions, and receive are represented in BEAM instructions.
OTP as the Core of Your Application Part 1
The post explains the Actor Model on the BEAM, then builds a Phoenix bookstore that reads from GenServers in later parts. Here it sets up the app, scrapes Manning data, and seeds Postgres.
The BEAM has Spoiled Me
Greg Vaughn says BEAM-style fault tolerance reduced his fear of crashes, made processes and idempotency part of his default Elixir practice, and led him to think in systems rather than web apps.
Elixir and ETS Alchemy
The post explains what ETS is, when it makes sense to use it, how table options and ownership affect behavior, and what to watch for when using ETS in production.
Concurrency In The Erlang VM
The page explains why Erlang is built for concurrency, using lightweight actor-like processes, message passing, and the BEAM scheduler to support fault-tolerant, distributed systems.
Elixir Digest #209 for July 01, 2019
Digest edition with Elixir v1.9 releases feature, Phoenix Universal/App Links, BEAM–Rust integration, Phoenix LiveView live_link, and property-based testing for stats.
