Skip to main content

Processes for Elixirs

Elixir processes are lightweight units of concurrency managed by the BEAM, not operating system threads. Each has its own heap and mailbox, shares no memory with others and communicates by sending messages with send and receive. Thousands can run at once, which is the basis of Elixir concurrency.

Stage: Concurrency · Part of the Elixir roadmap · Last reviewed 19 November 2026

What to learn in Processes

Processes interview questions

How is an Elixir process different from an OS thread?

A BEAM process is far lighter: it starts with a small heap, is scheduled by the VM and is garbage collected independently. Processes share no memory and only communicate through messages, so a crash in one does not corrupt another process's data.

What is the difference between link and monitor?

A link is bidirectional: if one linked process exits abnormally, the other receives an exit signal and dies too unless it traps exits. A monitor is one-way and only sends a :DOWN message to the watcher, leaving it alive to decide what to do.

Where Processes fits in the Elixir roadmap

Processes belongs to the Concurrency stage (intermediate level). Processes on the BEAM.

Back to the full Elixir roadmap