[pairing]

When it's said that Elixir is highly distributed what is sometimes left off is "within a datacenter". BEAM / Erlang / Elixir clusters are not intended to be used/scaled across datacenters due to latency issues.

So if you are an AWS user for example and want to be in multiple availability zones the Elixir distribution model will not scale and you'll have to use the same techniques and tools other languages use for distribution.

With that in mind, I think the whole distribution buzzword is way over hyped since the majority of companies will be leveraging cloud platforms like Azure, AWS, Google Cloud, etc.

I write Elixir code daily because it's an awesome language to write in and not for the distribution features.

[nivertech]

you are not supposed to use Erlang built-in distribution in the main path in production anyway.

I only use it for management and non-critical low t-put control flow, never for the high t-put and/or data flow.

For high t-put you need to implement your own protocols over TCP or something like ZeroMQ.

Some major Erlang-based open-source projects (ejabberd, riak, RabbitMQ) use built-in distribution and that's why they usually either slow or fail under high load in production.