Re:Swift Distributed Actors
by acjohnson55 on Friday October 29, 2021 @10:48AM
(#29039121)
I don't know if that's true. In the Scala and Java worlds, a library called Akka provides distributed actors as a library. As far as I know, what you describe isn't a limitation. See https://doc.akka.io/docs/akka/2.5.32/general/supervision.htm...
It is a limitation. If the VM on the other machine is killed, or kills the thread, you'll never know that happened, and why. Well, you can probably ping the process and what not :)
Compare Erlang's error handling and monitors: https://erlang.org/doc/reference_manual/processes.html#error...
Re:Swift Distributed Actors
by acjohnson55 on Saturday October 30, 2021 @03:37AM
(#29046826)
I would assume Erlang is doing some type of heartbeat at the runtime level. You can always do this in your protocol if you absolutely need to. I know that in Akka Cluster, you configure this to set the rules for a node to be considered alive in the cluster, and if it's dead, all the actors hosted on it will be considered dead, too.
In a distributed system, I'm pretty certain you cannot guarantee receipt of an expected message, no matter what you try to do.
Re:Swift Distributed Actors
by ProfHewitt on Friday October 29, 2021 @11:59AM
(#29040060)
Erlang has absolutely no security :-(
The reason is: you want certain guarantees. For example, in Erlang you can set up a monitor on a process, and when that process exits for any reason, you get a notification, {EXIT, Reason}. Even if that reason was a catastrophic failure of some sort.
If this is implemented as a library, then the runtime can kill your code at any time, and you'll never know what happened.