Architecting 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.
Loading…
ReadMeFeed / Community knowledge
#fault-tolerance
Real questions. Useful conversations. Find the people who know your stack.
Using 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.
erlangSelenium Grid 4 session persistence limits during incremental migration
We are planning to migrate a small Selenium Grid deployment to Grid 4 incrementally, with the goal of avoiding interruptions to in-flight browser sessions. The documented architecture separates the Router, Distributor, Session Map, and Node processes, and nodes support graceful draining so running sessions can finish before a node exits. However, the Session
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
gleam