Moving Beyond Try-Catch: Implementing Supervision in Akka
Stop fighting exceptions with try-catch. Learn how Akka's 'Let it Crash' philosophy and supervision strategies allow you to build self-healing systems by isolating failures.
Loading…
ReadMeFeed / Community knowledge
#fault-tolerance
Real questions. Useful conversations. Find the people who know your stack.
akka
scalaMoleculer Built-in Fault Tolerance: Policy Composition Without Library Sprawl
Moleculer ships timeout, retry, circuit‑breaker and bulkhead middlewares that compose declaratively via a policy object—eliminating the need for external resilience libraries. Understand the execution order, state sync, and cancellation wiring.
moleculerImplementing Fault-Tolerant Worker Patterns with Erlang OTP Supervisors
Learn how to implement Erlang OTP supervisors to ensure fault tolerance. This guide covers restart strategies, child specifications, and how to prevent infinite restart loops in concurrent systems.
Moving Beyond Try-Catch: Implementing Erlang's 'Let it Crash' Philosophy
Stop fighting runtime errors with nested try-catch blocks. Learn how Erlang’s fault tolerance patterns let you build self‑healing systems using supervisors and the "Let it Crash" philosophy.
Stop Defensive Coding: Implementing Erlang Supervision Trees
Stop using try-catch for everything. Learn how Erlang's 'Let it Crash' philosophy and supervision trees create resilient systems by isolating failures and automating recovery.
erlangArchitecting Fault‑Tolerant Concurrent Services with Gleam and the BEAM
Learn how to build resilient concurrent systems using Gleam's static type system and the BEAM's Actor model, focusing on supervisor patterns and data boundaries.
gleamUsing Erlang Supervision Trees to Embrace the Let‑It‑Crash Philosophy
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.
How does Akka handle an actor's mailbox when a Kill message triggers a supervisor restart?
In an Akka system, an actor can be terminated by sending a Kill message, which throws an ActorKilledException and is processed by the actor's supervisor. Assuming the default supervisor strategy (which stops the actor and then restarts it), what happens to the messages that were already in the actor's mailbox at the moment the Kill was processed? Are those m