[zeromq-dev] Queuing to multiple workers and receiving multiple responses as a single multi-part message.

[John Smith]

Sorry it has taken me so long to get back to you, I have not explained
myself very well :-).

Basically, my idea was to have a forum where, to achieve high scalability,
data would be split among multiple databases, perhaps by the modulo 3 of the
message id if you had 3 databases.  If there was then one worker per
database, then every time a process requested say ids 1 to 100, a request
would need to be made to each worker, and each worker would return the
messages stored in its database in parallel.

I think I would need to use an async pub/sub type architecture back
end, with a front end which took all the events and matched them up to the
original request.

On Sun, May 9, 2010 at 10:06 PM, Martin Sustrik <sustrik at 250bpm.com> wrote:

>
>
> First of all, can you explain what are you trying to achieve? Why
> process same data on multiple nodes? Is it meant to work as a hot-hot
> failover?
>
> Martin
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20100510/662ad617/attachment.htm>