# Distributed application - network split

**URL:** <https://forum.elixirforum.com/t/distributed-application-network-split/10007>\
**Category:** Questions\
**Tags:** erlang, distributed-systems\
**Created:** [November 10, 2017, 3:50pm UTC](https://forum.elixirforum.com/t/distributed-application-network-split/10007 "2017-11-10T15:50:38Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![hubertlepicki](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/hubertlepicki/32/6822_2.png) [@hubertlepicki](https://forum.elixirforum.com/u/hubertlepicki)\
**Post date:** [November 11, 2017, 7:14am UTC](https://forum.elixirforum.com/t/distributed-application-network-split/10007/7 "2017-11-11T07:14:39Z")

</div>

Yes, I’m not looking at it from distributed state point of view at all just yet. As I originally pointed out, the objective is being able to fail over to backup nodes and recover from failure.

My current thinking is that the built-in `dist_ac` is not suitable for any cloud-based deployment, as it was designed for co-located servers. It does not handle well network splits, resulting in brief freezes of nodes when it happens, and then can’t re-join on it’s own the cluster and restore the topology of apps running on top of the cluster.

I am experimenting now with @bitwalker 's libcluster, as a low-level cluster manager. [libcluster — libcluster v3.5.0](https://hexdocs.pm/libcluster/readme.html) with possibly swarm running on top, or a custom solution. I’d need to implement EC2 clustering strategy, I think too.

---

_[View the full topic](https://forum.elixirforum.com/t/distributed-application-network-split/10007)._