4 ms·
It’s true even with distribution, see e.g.: http://erlang.org/faq/academic.html#idp33052176 http://erlang.org/faq/academic.html#idp33052176 http://erlang.org/
by ramchip 6y ago
It’s true even with distribution, see e.g.:
http://erlang.org/faq/academic.html#idp33052176 http://erlang.org/faq/academic.html#idp33052176
http://erlang.org/pipermail/erlang-questions/2017-September/093666.html http://erlang.org/pipermail/erlang-questions/2017-September/...
- to11mtm 6y agoHuh. Never actually looked into HOW it worked in erlang, but basically it looks like it works the same way as Akka/AkkaDotNet; VM skates on top of the underlying transport's ordering guarantees. For a long time I was curious how Akka Artery preserved message ordering for it's 'dedicated large message' lane. in short it really just means you are dedicating a specific TCP or Aeron connection dedicated to those actors, there's no magic ordering sauce underneath. (just a little disappointed to find that out, but appreciate the simplicity upon consideration.)
- ramchip 6y agoYep. Erlang uses a single TCP connection between each pair of nodes. Older versions had problems with large messages blocking heartbeats (and other messages) for a long time, but that's been resolved last year in https://github.com/erlang/otp/pull/2133 https://github.com/erlang/otp/pull/2133.