I suggested it precisely because it’s got the same API as normal Registry, I also use it in production and it works fine.
hubertlepicki
schneebyte
sleipnir
Thanks.
When I saw the main comment what caught my attention was that you need a strong reference but following the principle of locality transparency, in this regard Spawn would help since you would just name your actors and be able to call them in a transparent way.
If you used the SDK available for Elixir you would be able to use Spawn just by configuring some environment variables without needing to use k8s. This is not how we recommend using it since you, in this case, would have to take care of the infrastructure yourself. But you might want to go along those lines.
Regarding the database, this is only mandatory for stateful actors. When using stateless actors you don’t need to connect to a database.
We could try to make a POC or something if we could get more details on its architecture. But there are some example repositories that can help you get a more general idea of the concepts.
0
mudasobwa
Creator of Cure
Well, there are a lot of good libraries above, but as I see the problem statement, one does not need any external library, nor even pg here.
Just name a process as {:global, Name}, and make sure the nodes are connected (by calling Node.connect/1 and checking it with Node.list/0.
Then :global.whereis_name/1 will give you a remote PID back, and you might use all the functions from GenServer using {:global, Name} as a remote process name.
2
schneebyte
For all GenServer calls/casts/etc you could use a helper function via() or @via macro with Application env.
And could use {atom, node} if the server is locally registered at another node or {:global, name}
0