News for hackers. Stuff that matters.
Re:.NET Orleans by Jtsummers on Monday October 05, 2020 @06:16PM (#24692666)
> - Orleans doesn't have any ordering guarantees. While this is not a firm requirement of the Actor model itself, both Erlang and Akka guarantee ordering between a given Sender-receiver pair (i.e. messages sent from A to C will be sent in order)

I thought Erlang only guaranteed that if the processes are on the same node. Is that not correct?

Re:.NET Orleans by ramchip on Monday October 05, 2020 @06:49PM (#24692922)
Re:.NET Orleans by to11mtm on Monday October 19, 2020 @03:19PM (#24829843)
Huh. 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.)

Re:.NET Orleans by ramchip on Wednesday October 21, 2020 @07:58AM (#24846918)
Yep. 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.