A "stateless" protocol would be one where your message has to contain all the information needed to handle it, so that the server contains no state. It sounds like a very large constraint. I work on a large load-balanced set of microservices, and they're all stateful, using shared state via a postgres database, so it doesn't matter which service instance my requests go to, since all of them contain the correct state.
What is it that you are trying to do? On Sun, Jun 25, 2017 at 1:51 PM, <[email protected]> wrote: > Hi, > > a few days ago I posted a question here regarding the combination of > Zeromq and Docker Swarm. > > As a follow up to this thread. Since it is not possible to really use a > stateful connections with the load balancer provided by Docker Swarm, I am > curious if it is possible to write distributed architectures with entirely > stateless protocols? > > Thanks, > > Florian > > _______________________________________________ > zeromq-dev mailing list > [email protected] > https://lists.zeromq.org/mailman/listinfo/zeromq-dev >
_______________________________________________ zeromq-dev mailing list [email protected] https://lists.zeromq.org/mailman/listinfo/zeromq-dev
