Any load balancer is going to pick between your servers at random, as far as you're concerned. The way this is typically handled is that your server instances use some kind of shared state, like a shared database, filesystem, quorum, or any other form of shared state so that it doesn't matter which server the message gets routed to. These are called "stateless" services, if you want to search for some reading material.
Alternately, you use persistent network connections, because most load balancers will maintain a TCP connection, but they're also pretty ruthless at closing idle connections, so this is more error prone. On Sat, Jun 17, 2017 at 2:39 PM, <picfl...@web.de> wrote: > Hi all, > > I have been using Zeromq for quite some time for all message related > tasks, but combining it with Docker Swarm built-in load balancing causes > me some issues. > I cant quite wrap my head around how to write persistend network protocols > when the Docker Swarm load-balancer on top can reroute my message to > any of the scaled receiver instances. Has someone here experiences with > this setup? > > Thanks a lot, > Florian > > _______________________________________________ > zeromq-dev mailing list > zeromq-dev@lists.zeromq.org > https://lists.zeromq.org/mailman/listinfo/zeromq-dev >
_______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org https://lists.zeromq.org/mailman/listinfo/zeromq-dev
