3 ms·
One useful piece of advice I recall, perhaps from Mahesh Paolini-Subramanya, was to write defensive code for predictable errors, despite the happy path coding t
by macintux 8y ago
One useful piece of advice I recall, perhaps from Mahesh Paolini-Subramanya, was to write defensive code for predictable errors, despite the happy path coding that Erlang allows.
So losing connectivity to a database should not result in a process failure, and thus is something that a supervisor should never have to deal with.
You’re right that there is no silver bullet internal to the language. Even the BEAM itself can fail.
- yellowapple 8y agoBetter yet: add another layer of supervision. Erlang processes are cheap. Might as well take advantage of that.