Great idea, Erlang is very good for such tasks. Native communication between nodes, very high availability and fault tolerance (native as well) using &quot;actor model&quot;[1] and good performance. As an example, in one of my previous companies we  built a message broker, which was able to keep 35K keep-alive connections on Amazon Medium EC2 instance and there still were reserves in CPU and Memory.<p>Plus it&#x27;s easier to learn it than it seems first time when you see it. Most of our Erlang-developers came from other languages, but they learned basics very quick: 1-2 days until the first commit on production.<p>The only one thing, it&#x27;s not so easy to debug it in the beginning. But it&#x27;s a question of practice, I think.<p>[1] <a href="http:&#x2F;&#x2F;learnyousomeerlang.com&#x2F;introduction#what-is-erlang" rel="nofollow">http:&#x2F;&#x2F;learnyousomeerlang.com&#x2F;introduction#what-is-erlang</a>