[zeromq-dev] zeromq-dev Digest, Vol 15, Issue 10

[picflo_2 at web.de]

Hi,

thanks that response.
I thought about this stateless approach, but dont I lose many advantages from stateful connections?
In Mr. Hintjens book much is said about how to write stateful protocols, to ensure certain qualities
like alive counter service and so on.

So whats the best solution if so to combine those two worlds, docker swarm and zeromq?

Thanks again
 
 

Gesendet: Dienstag, 20. Juni 2017 um 12:00 Uhr
Von: zeromq-dev-request at lists.zeromq.org
An: zeromq-dev at lists.zeromq.org
Betreff: zeromq-dev Digest, Vol 15, Issue 10
Send zeromq-dev mailing list submissions to
zeromq-dev at lists.zeromq.org

To subscribe or unsubscribe via the World Wide Web, visit
https://lists.zeromq.org/mailman/listinfo/zeromq-dev
or, via email, send a message with subject or body 'help' to
zeromq-dev-request at lists.zeromq.org

You can reach the person managing the list at
zeromq-dev-owner at lists.zeromq.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of zeromq-dev digest..."


Today's Topics:

1. Re: Zeromq with Docker Swarm (Marcin Romaszewicz)


----------------------------------------------------------------------

Message: 1
Date: Mon, 19 Jun 2017 10:13:16 -0700
From: Marcin Romaszewicz <marcin at brkt.com>
To: ZeroMQ development list <zeromq-dev at lists.zeromq.org>
Subject: Re: [zeromq-dev] Zeromq with Docker Swarm
Message-ID:
<CACKFMAUROK5bHh1TA6AgnnPtLgx9h-Dx0FN2DbiUTnoo4ta05A at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

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, <picflo_2 at 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 at lists.zeromq.org
> https://lists.zeromq.org/mailman/listinfo/zeromq-dev[https://lists.zeromq.org/mailman/listinfo/zeromq-dev]
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20170619/9d8169e9/attachment-0001.html[https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20170619/9d8169e9/attachment-0001.html]>

------------------------------

Subject: Digest Footer

_______________________________________________
zeromq-dev mailing list
zeromq-dev at lists.zeromq.org
https://lists.zeromq.org/mailman/listinfo/zeromq-dev[https://lists.zeromq.org/mailman/listinfo/zeromq-dev]


------------------------------

End of zeromq-dev Digest, Vol 15, Issue 10
******************************************