OTP for Elixirs
OTP, the Open Telecom Platform, is the set of behaviours and conventions for building reliable Elixir applications. GenServer wraps a process with a standard callback interface for state and requests, and Supervisors restart crashed children according to a strategy, following the let-it-crash philosophy.
Stage: Concurrency · Part of the Elixir roadmap · Last reviewed 19 November 2026
What to learn in OTP
- Implement a GenServer with init, handle_call and handle_cast callbacks
- Choose between call and cast based on whether a reply is needed
- Define a supervisor with child specs and a restart strategy such as one_for_one
- Design a supervision tree so a failure restarts only the affected part
- Name processes with a Registry or a registered name to find them reliably
OTP interview questions
What does let it crash mean in Elixir?
Instead of defending against every possible error inside a process, you let it fail fast and have a supervisor restart it in a known good state. This keeps code simple and recovers from unexpected faults, provided state is rebuilt cleanly on restart.
When should you use GenServer.call instead of cast?
Use call when the caller needs a result or confirmation, since it is synchronous and has a timeout that defaults to five seconds. Use cast for fire-and-forget updates, remembering that cast gives no delivery acknowledgement and can let a slow server's mailbox grow.
Where OTP fits in the Elixir roadmap
OTP belongs to the Concurrency stage (intermediate level). Processes on the BEAM.
Other units in this stage
Back to the full Elixir roadmap