Comment by munchler

I've always found myself in fundamental disagreement with the Erlang/Elixir philosophy.

    Resilience, within the context of this presentation, and the philosophy of Erlang, would be the capability to recover from errors while unattended.

I prefer systems that don't fail quite so smoothly. Take this example:

    The application runs out of memory due to too many transactions being processed at once. The problem happens once every day. However the system gracefully recovers, and the team is able to resolve the issue peacefully without the problem escalating to an active incident.

If I was funding development of such a system, I would find this situation unacceptable. I'm paying for an application that doesn't crap out in production every single day, not one that "gracefully recovers" after each such event so the dev team can "peacefully" manage it. The users whose data is lost during these incidents probably wouldn't feel quite so peaceful about it, either.