[zeromq-dev] Clustering xPub xSub Proxies

James Harvey JHarvey at factset.com
Tue May 19 18:55:05 CEST 2020


I do something similar in the “cloud”.

I have upstream load balancer connected to 3 proxies.
I have a downstream load balancer connected to 3 other proxies
All of the above are in a cloud scale set/group of 3 VM’s, each VM contains 1 upstream and 1 downstream proxy.

Using the magic of the cloud (or you could use DNS) The upstream proxies know the IP addresses of the downstream proxies and connect to them.  This is a little more cloud specific but I use a python application to get the addresses from the scale set info and inject that into the proxies using a zeromq socket.

Now if any VM in the scale set goes down the system will still work as expected.

Also you can scale the number of VM’s up and down based on load.

From: zeromq-dev <zeromq-dev-bounces at lists.zeromq.org> On Behalf Of Justin Schwartz
Sent: 19 May 2020 17:41
To: zeromq-dev at lists.zeromq.org
Subject: [zeromq-dev] Clustering xPub xSub Proxies

Our scenario: we have multiple ZeroMQ publishers and subscribers running in the cloud in a private subnet. To enable external subscribers or publishers, we route traffic through a Load Balancer that sits in a public subnet. All of the traffic, both inside and outside the cloud, connects to a ZeroMQ broker that runs an xPub/xSub proxy. All of this works well, except for the fact that we have a single point of failure – a single broker application.

Is it possible to cluster multiple xPub/xSub proxies together? How would we go about doing so?

The goal here is to ensure that if one broker is inaccessible, due to network partition or is in the process of being upgraded that the system doesn’t experience interruptions.

Thank you

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20200519/acfbf0e9/attachment.htm>

More information about the zeromq-dev mailing list