> erlang/elixir: Never used this, but seems ideal for highly scalable concurrent architecture and highly scalable process choreography. Erlang's primary reason

> erlang/elixir: Never used this, but seems ideal for highly scalable concurrent architecture and highly scalable process choreography. Erlang's primary reason for existence is fault tolerance. High concurrency and scalability is just a bonus. Consider hot code reloading, supervision trees, links and monitors, D/ETS and Mnesia, location-agnostic message passing. These have nothing to do with scalability. You use Erlang when you absolutely have to have the system continue to work 24/7/365 in perpetuity even in the presence of software errors.