[zeromq-dev] Zyre clustering in malamute broker

[Mario Steinhoff]

Maybe thats better.
Having a local broker in every service node sounded like a crazy
awesome idea at first but I think I don't really have the need for
that.

The speculative design itself sounds interesting.
Why not just mark it as "this is something you could do but we never
had the need for it"?

--
Mario

2016-03-16 21:40 GMT+01:00 Pieter Hintjens <ph at imatix.com>:
> It's not implemented. You're not the only lazy bastard around :)
>
> To make this work is non-trivial. Zyre would make it easy to find
> other instances. What you do then is to exchange subscriptions and
> then cross publish. And then the same for mailboxes and services. A
> federation model.
>
> I may update the whitepaper to remove all the speculative design.
>
> -Pieter
>
> On Wed, Mar 16, 2016 at 7:36 PM, Mario Steinhoff
> <steinhoff.mario at gmail.com> wrote:
>> Hey everyone,
>>
>> the malamute discussion whitepaper says:
>>
>>> A peer-to-peer cluster of Malamute brokers serving a cloud, where each system on the cloud runs one Malamute broker. Applications connect to their local broker over IPC, and the brokers talk to each other over TCP. Malamute uses the Zyre clustering technology to rapidly discover and connect to new Malamute brokers.
>>
>> I am a lazy bastard and haven't checked the code yet.
>>
>> Is this functionality actually implemented?
>>
>> If not, what would I have to do?
>>
>> Mario
>> _______________________________________________
>> zeromq-dev mailing list
>> zeromq-dev at lists.zeromq.org
>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev