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.
Learn how to use gleam_otp to implement Erlang gen_server behaviours and supervision trees in Gleam, with concrete build and verification steps for the Erlang target.
Explains how to use Elixir GenServers for safe state management, covering requirements, minimal design, process boundaries, supervision, monitoring, and when to adjust the architecture.
A concise architecture note that outlines requirements, the minimal supervision‑tree design, trust boundaries, operational checks, failure modes, and triggers for redesign when using Erlang/OTP for resilient services.
Supervision strategy is a claim about which Erlang processes depend on which. Pick it from the dependency graph, then confirm it with a deliberate kill on a test node.
Learn how Erlang’s Let it Crash philosophy uses supervision trees to isolate faults, restart workers safely, and keep systems self‑healing without complex defensive code.
erlang
gleam