Operations for Elixirs
Elixir operations covers running an application in production. A release, built with mix release, bundles the compiled code and the Erlang runtime into a self-contained package, and runtime configuration and observability tools such as Telemetry, logging and the observer help you watch a live system.
Stage: Phoenix and Production · Part of the Elixir roadmap · Last reviewed 19 November 2026
What to learn in Operations
- Build a release with mix release and start it as a service
- Set configuration at runtime in runtime.exs from environment variables
- Emit and attach Telemetry events to track request and query timings
- Inspect a running node's processes and memory with observer or remote iex
- Cluster nodes and understand the basics of distributed Erlang
Operations interview questions
Why use a release instead of running mix phx.server in production?
A release is a self-contained artefact with the compiled code and the Erlang runtime, so the target machine needs neither Elixir nor Mix. It starts faster, uses less memory, and supports runtime configuration and remote shell access to the live node.
What is the difference between config.exs and runtime.exs?
config.exs is evaluated at compile time, so values are baked into the build. runtime.exs runs when the release boots, which lets you read secrets and environment variables such as the database URL from the deployment environment.
Where Operations fits in the Elixir roadmap
Operations belongs to the Phoenix and Production stage (advanced level). Ship.
Other units in this stage
Back to the full Elixir roadmap