On Wed, 2017-08-02 at 09:25 -0400, Bill Torpey wrote: > The problem of topic discovery keeps coming up, and one of the first > approaches recommended is to use a broker. That makes sense from the > point of view of simplicity, but it has several disadvantages in the > areas of scalability and availabilty. > > An obvious (?) solution would be to use a “topic broker" to connect > publishers and subscribers, but to have the actual messages flow > directly from publisher to subscriber. There are several commercial > solutions that use this approach (e.g., Wombat, LBM) and it seems to > work reasonably well. > > I’m new to ZeroMQ and am curious if anyone in the community has taken > this approach? Is there a simple way of “wiring up” ZeroMQ to make > this work? Or would this require some custom development on top of > core ZeroMQ functionality? > > To be clear, I’m not interested in solutions that are built on top of > multicast — for a number of reasons that is simply not a practical > approach in my environment. And while there are projects associated > with ZeroMQ that seem to address topic discovery (i.e., Zyre, > zbeacon), as far as I can tell they all (a) depend on multicast, and > (b) deliver subscribe/unsubscribe requests over the same stream as > actual data messages. > > I have a general idea how to build this, but it’s a fair bit of work, > esp. when edge cases are taken into account. Plus, I don’t want to > look like an idiot when someone says “Why didn’t you just …?”. > > Any tips, hints or suggestions would be much appreciated! Thanks!
Note that zyre needs multicast (in ipv6, broadcast in v4) only with zbeacon mode, but with zgossip mode (ie: with a well-known and pre- configured "hub") it uses just regular unicast. -- Kind regards, Luca Boccassi
signature.asc
Description: This is a digitally signed message part
_______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org https://lists.zeromq.org/mailman/listinfo/zeromq-dev
