Isn't this also solved by just load balancing so that the customer ends up reconnected to a healthy node while the downed node is replaced? We run our Scala ap

Isn't this also solved by just load balancing so that the customer ends up reconnected to a healthy node while the downed node is replaced? We run our Scala apps on Aurora/Mesos behind a load balancer (hundreds of instances for just one app). If there's an issue that can't be handled within the app and error rates breach a given threshold, Aurora just kills the instance and creates a new one on another host.