[erlang-questions] Serfdom erlang implementation (gossip client)?

[Mark Allen]

I looked at the golang implementation several weeks ago, but I had the sense that the underlying serfdom network protocol was evolving too rapidly to really have a good go at writing some kind of Erlang client at this point in time.  (Maybe it has settled down now - I haven't really looked again recently.)

I agree that it would be really nice way to send information around to a cluster of Erlang VMs if you can tolerate how gossip protocols behave so it's definitely on my radar.  If anyone else is interested in working on this, I would be willing to help :)

In the meantime, if you want to see an Erlang-y implementation of a gossip protocol as a model, you could look at how Basho did its anti-entropy stuff in riak core (as one example)

https://github.com/basho/riak_core/blob/develop/src/riak_core_gossip.erl

(Note: this is the "develop" branch which is kind of the bleeding edge of the codebase. Try 1.4 branch if you want a "stable" view of the code.)

Mark
From: Max Lapshin <max.lapshin@REDACTED<mailto:max.lapshin@REDACTED>>
Date: Sunday, January 12, 2014 11:27 AM
To: Erlang-Questions Questions <erlang-questions@REDACTED<mailto:erlang-questions@REDACTED>>
Subject: [erlang-questions] Serfdom erlang implementation (gossip client)?

Mitchell Hashimoto (author of Vagrant and Packer) has another project, it is serf.

Serf is an implementation of protocol that maintains cluster of nodes. Sounds like a replacement to erlang distribution, but it is a bit different.

At first, it doesn't do any magic interconnection with transparent Pid and message passing to other nodes. It only maintains persistence of nodes in a more probabilistic manner (UDP pinging).

Has anyone looked at it? Maybe someone has tried to implement it?

I'm interested in this approach because it doesn't require to give full access to local system for remote user as it happens with erlang interconnect.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140113/ccccf823/attachment.htm>