daviaws
Is Horde Registry really distributed?
I was trying to address a distributed genserver, which is ensured to be unique by the Horde.DynamicSupervisor supervision tree.
I can check this with Supervisor.which_children - showing me local and remote pids.
- I can derive recursively which_children to child supervisors of Horde and so address process remotelly.
But the Register should also do it.
“A distributed process registry.”
“Local changes to the registry will automatically be synced to other nodes in the cluster.”
But reading the code of register/lookup
https://github.com/derekkraan/horde/blob/master/lib/horde/registry.ex#L222-L230
It’s working over :ets.
Not only this but I can use Horde.Registry to register the same key over 3 nodes.
![]()
![]()
Not only this. For each node, Horde.Registry shows me different local pids.
Both Horde.DynamicSupervisor, and Horde.Registry on my application children list.
Am I missing something? Because :ets is a local resource. And even if the Registry is said to be distributed and it sure have deltacrdt configured on start.
I could not validate distributed behavior.
Most Liked
derekkraan
Hello, I’m the author and sole maintainer of Horde.
Just popping in to answer a few of your questions:
Is Horde Registry really distributed?
Yes, it is backed by DeltaCRDT, which has leaderless syncing. Updates that come in are written to an ets table for quick read access. Writes go through the CRDT.
Am I missing something?
It looks like you have configured Horde.NodeListener for your Horde.DynamicSupervisor, but not for your Horde.Registry. I checked, and the guides are not super clear on this, probably owing to the order in which things were built (Horde.NodeListener was added after the guides were written).
Others have mentioned this already, perhaps you should re-read their responses.
Unmaintained
Horde is a library that, as I have learned, has some limitations, but still remains useful to quite a few people (>9k downloads last 7 days). I don’t have the time nor the interest in large development efforts for the project, and there are not a lot of new PRs coming in to the project.
I try to stay on top of things, but the obvious bugs have been ironed out a long time ago, and aside from a few small issues, I would say that Horde is doing fine.
Finally, I will note that Horde is provided free of charge and without any kind of guarantee that it will work.
adw632
You may be referring to the old slow pg that pg2 replaced.
The docs for the ‘new’ pg in OTP/23 that deprecated pg2 explicitly states that pg is eventually consistent. The source code for pg indicates it was contributed by WhatsApp.
pg doesn’t have a long list of critical crashing problems unlike some other options mentioned here.
In theory, theory and practice are the same. In practice they are not.
anuaralfetahe
I have been working on a comparable library ProcessHub. Although it’s still in the alpha stage, active development is ongoing.
I’m not going to mention the other libraries already pointed out but alternatively, you may want to explore Swarm.
While you could develop your implementation using the pg module, which is robust and would perform well in your described scenario, you may encounter challenges when the distribution model becomes more complex.
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance










