[erlang-questions] massive distribution

Kevin A. Smith <>
Tue Dec 1 16:24:48 CET 2009


On Dec 1, 2009, at 10:11 AM, Peter Sabaini wrote:

> On Tue, 2009-12-01 at 11:32 +0100, Roberto Ostinelli wrote:
>>> If you're talking about the built-in Erlang distribution mechanisms --
>>> FWIW: in a quick test I did a while ago I had trouble keeping stable
>>> connections for more than ~80 connected nodes. I must admit I was a bit
>>> surprised as the "Efficiency Guide" seems to imply that the number
>>> should be much higher (?).
>>> 
>>> Possibly the number of known (but not connected) nodes can be higher
>>> than this.
>>> 
>>> HTH,
>>> peter.
>> 
>> thank you peter.
>> 
>> 80 connected nodes seems a low number if one seriously need to build
>> cloud applications.
> 
> I guess that depends on the application and what "serious" means :-)
> 
> 
>> i guess that one needs to develop his own mechanisms for
>> interconnecting nodes in a way more similar to a custom 'mesh
>> networking' [pardon the conceptually wrong extension of this term]?
>> would that be more appropriate, to your belief?
> 
> As Kevin hinted at, one can use Erlangs' distribution protocol without
> using automatic connection handling. OTOH, if you for instance need more
> security than Erlangs distribution mechanism provide, it might be wise
> to invest in a custom protocol anyway. FWIW, I imagine the data
> serialization/deserialization functions could be reused.
> 

I've rolled my own clustering bits over TCP sockets for a couple of clients. term_to_binary, binary_to_term, and {packet, 1/2/4} can significantly ease the work involved. It allows you to focus on the security bits and allow Erlang to handle reassembly and serialization.

Just my $0.02 worth...

--Kevin

> peter.
> 
>> cheers,
>> 
>> r.
> 
> 
> ________________________________________________________________
> erlang-questions mailing list. See http://www.erlang.org/faq.html
> erlang-questions (at) erlang.org
> 



More information about the erlang-questions mailing list