Let It Crash: Building Fault‑Tolerant Apps with Erlang Supervision Trees
Discover how Erlang’s OTP supervision trees and the "Let It Crash" philosophy let you build self‑healing distributed systems without defensive error handling.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Discover how Erlang’s OTP supervision trees and the "Let It Crash" philosophy let you build self‑healing distributed systems without defensive error handling.
Learn how to build a minimal OTP supervision tree in Erlang: requirements, design, trust boundaries, operational checks, failure modes, and when to redesign.
How OTP supervisors restart failed workers: one_for_one vs one_for_all vs rest_for_one, a worked supervisor module with map child specs, intensity/period escalation, and the state-loss and crash-loop mistakes to avoid.
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.
An architecture note on using a single supervised GenServer for serialized state in Elixir: requirements, a minimal implementation, trust boundaries, production checks, and the conditions that should push you to ETS, sharding, or distribution.
Eliminate password friction by implementing Supabase Magic Links. Learn how to set up passwordless OTP authentication, handle redirects, and secure your flow against phishing.
A technical decision guide for Erlang/OTP state management, comparing ETS, persistent_term, and the process dictionary based on latency, concurrency, and mutability.
GenServer serializes access to state without locks. This post builds a working key-value store, puts it under supervision, and explains when a single process becomes the bottleneck.