[lobstrosity420]

Is your argument that the application gracefully recovering from the scenario will somehow make the dev team accommodated?

Hard crashes are not an acceptable substitute for observability, or continuous improvement.

[munchler]

I'm not sure what you mean by "accommodated".

This example doesn't even rise to the level of an "active incident" in the Erlang philosophy. In other words, it's not a bug, so there's no urgency to improve it.

[lawn]

You're just misunderstanding the philosophy.

It's still a bug that should be fixed, it's just that the effects are better contained thanks to the ability to self-heal.

[lobstrosity420]

If there is data loss it’s an incident, full stop. Your observability layer should be letting you know.