Let me ask one question then: how do you expect your app to behave when you drop connections to the database because there is a very quick netsplit of few seconds?
The supervisor model in Elixir was never about the fault tolerance at the load balancer or between nodes (it could be done like that but you would need to write a lot of infrastructure to get this working, i.e. it is not there out of the box). It is about bringing a reasonable model to reason about errors inside the programming language.
And the behaviour Elixir provides here can be achieved in all programming languages. I am pretty sure Java, Ruby, Python, Haskell, etc can all reconnect to the database when the database disconnects, the case for Elixir is that achieving the same behaviour is done more reliably and with simpler idioms.
So I agree with @keathley. Those two should not really be compared and if someone was expecting the value for Erlang/Elixir to come from the fault tolerance at such a high level, it is no surprise their expectations are not being met. But preferably those expectations should not have been set in the first place.
