4 ms·

> This is because we are not replicating the data between the instances. This is a problem Elixir is built for… What feature is this and does it not really exi

• silbermm 4y ago
  The feature is distributed message passing (basically an Actor model) https://www.erlang.org/doc/reference_manual/distributed.html https://www.erlang.org/doc/reference_manual/distributed.html You can get this in other languages with the help of middleware like RabbitMQ or Kafka, but not many languages have it built in.
• nesarkvechnep 4y ago
  You can’t get it in C# or Java. The BEAM virtual machine is build upon the idea of lightweight processes. You might get an imitation in other mainstream places but not the real thing. Take a look at the Actor Model if you haven’t heard of it.
  • mattfrommars 4y ago
    > might get an imitation in other mainstream places but not the real thing. Could you further elaborate on this? I am familiar with Actor Model. I had work related to Akka in Scala that works on the principles of Actor Model.
    • weatherlight 4y ago
      Erlang uses a preemptive scheduler for process scheduling, allowing for parallelization on multiple CPUs, while Scala distinguishes between thread-based and event-based actors. Thread-based actors can perform long-running computations without hindering other actors, but use more memory and scheduling overhead. Event-based actors are more lightweight but not suitable for parallelism as they execute on the same thread.