Hi newbie! We’ve done much of what you are proposing — unfortunately the “heavy lifting” (acks, timeouts, etc.) is proprietary, but we have recently made some of our code open-source: https://github.com/nyfix/OZ <https://github.com/nyfix/OZ>. It may give you some ideas, even if it ends up not being suitable for your project.
FWIW, I’m a big fan of plain old pub/sub — many users of ZeroMQ seem to prefer the addl. functionality provided by some of the other socket types, but personally I like the flexibility of simple pub/sub. Good luck! Bill > On Jun 5, 2020, at 10:19 AM, P S <[email protected]> wrote: > > Hello, > > I am newbie to ZeroMQ. I am looking at using ZeroMQ for the upcoming project > that has the following requirements: > Multiple components need to send messages to other components running on > geographically distributed machines > Each component also needs to receive messages sent by other components > Guaranteed delivery needed - perhaps ack / timeout / retry strategy needed > A mechanism to buffer messages locally on each component in case one of the > components is deemed to be unavailable (no ack) > A mechanism to re-send messages to the new component that has joined > Support of TLS on all communication > Based on what I have read so far, PUB / SUB with XPUB / XSUB appears to be a > good place to start. Any feedback on this or any other better strategy is > highly appreciated. > _______________________________________________ > zeromq-dev mailing list > [email protected] <mailto:[email protected]> > https://lists.zeromq.org/mailman/listinfo/zeromq-dev > <https://lists.zeromq.org/mailman/listinfo/zeromq-dev>
_______________________________________________ zeromq-dev mailing list [email protected] https://lists.zeromq.org/mailman/listinfo/zeromq-dev
