Let It Crash: Building Resilient Erlang Services with Supervision Trees
Discover how Erlang’s supervision trees let workers crash safely and recover automatically, keeping your node alive while keeping code simple.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Discover how Erlang’s supervision trees let workers crash safely and recover automatically, keeping your node alive while keeping code simple.
Use one_for_one leaf supervisors with intensity 5 in 60 seconds to isolate worker crashes in Erlang OTP. A worked supervisor init shows how restart type, shutdown and strategy contain failures and when the supervisor intentionally escalates.
Ballerina's sum-type error model and native fault-tolerance constructs make errors explicit in the type system and encode retry, timeout, and circuit-breaker policies into service bindings, shaping resilient trust boundaries and failure domains.
Learn how to architect fault‑tolerant, asynchronous MATLAB code with parfeval, covering requirements, minimal design, data isolation, operational checks, failure handling, and when to re‑design. Includes example code and verification steps.
Match Erlang OTP restart strategies to your failure domain so a crashing worker does not restart unrelated services.
Learn how to add and remove WebSocket connection processes at runtime with Elixir’s dynamic supervision, including a runnable example and key trade‑offs.
A child actor crashes mid-message. Should you Resume, Restart, Stop, or Escalate? Learn how to pick an Akka SupervisorStrategy based on state consistency, not just uptime.
Learn how the one_for_one restart strategy isolates failures in Erlang OTP supervision trees, see a concrete gen_server example, and understand when to use it.
Discover how Erlang’s OTP supervision trees and the "Let It Crash" philosophy let you build self‑healing distributed systems without defensive error handling.