[zeromq-dev] What pattern of ZeroMQ best to use for Relay server scenario?

[Brett Viren]

What you describe is almost:

  http://zguide.zeromq.org/page:all#Basic-Reliable-Queuing-Simple-Pirate-Pattern

The difference is you say you want clients to determine which backend
"worker" shall receive the task based on the client providing some
"name".  To provide that, the "load balancer" in that pattern will have
to be modified to route based on "name" instead a measure of load.  This
can be done straightforwardly by each worker providing a "name" in their
message sent after each REQ connect and the "load balancer" then
maintaining a "name" -> "router ID" lookup.

You might do well to read on to the next pattern in the guide to see how
to add heartbeating.

-Brett.

<giedrius.lukosevicius at advantes.tech> writes:

> What pattern of ZeroMQ best to use for Relay server scenario?
>
> Problem solving:
>
> 1.      There are many requestors/clients ( A,B,C )
>
> 2.      There are many external servers workers ( X,Y,Z )
>
> 3.      Need to set Relay server to serve requests from clients, forward it to specific worker (e.g.
> A->X,B->Y,C->Z), get respose from worker and forward it back to requestor/client.
>
> 4.      Relay server autorizes clients and then knows which server needs to send request by it's
> name.
>
>  
>
> My first impression was Marjodomo pattern , but not sure how to identify and keep track on specific
> worker..
>
> Please suggest!
>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> https://lists.zeromq.org/mailman/listinfo/zeromq-dev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20190401/39ab348d/attachment.sig>