3 ms·
That looks interesting! What's the distributed story of Ractor? Would you need a central store like Redis to serve as Actor registry? One of the promises of E
by jatins 2y ago
That looks interesting! What's the distributed story of Ractor? Would you need a central store like Redis to serve as Actor registry?
One of the promises of Elixir/Erlang is that you can call a process/Actor on different machine just like you can one on same once you put together a bunch of machines in a cluster
- stefanka 2y agoSeems to be supported > Additionally ractor has a companion library, ractor_cluster which is needed for ractor to be deployed in a distributed (cluster-like) scenario. ractor_cluster shouldn’t be considered production ready, but it is relatively stable and we’d love your feedback!
- kemiller 2y agoElixir/erlang/gleam also have the advantage that many libraries are written as servers and so automatically gain the benefits and resilience. Something all these actor frameworks can’t give you.
- brunoqc 2y agoWith gleam, how do you call an actor on another machine when you have a cluster? Do you need something like redis?
- doawoo 2y agoThe Erlang runtime and EPMD takes care of this for you. Every node in the cluster gets a name, so you can address it directly, and, every PID is unique across nodes on a cluster, so you can send messages to processes (actors) no matter where they are in the cluster. OTP is super powerful out of the box :)
- brunoqc 2y agoThanks! I'm taking a look at https://github.com/wmealing/gleam-distribution-demo/tree/main https://github.com/wmealing/gleam-distribution-demo/tree/mai... And https://github.com/wmealing/gleam-otp-design-principals/blob/main/gleam-otp-design-principals.org#starting-up-nodes https://github.com/wmealing/gleam-otp-design-principals/blob...