[zeromq-dev] High throughput Zero MQ messaging pattern.

[girish kumar]

Hi,

Thanks for your response. So, in that case I can have multiple threads in
my NIO based server will become publishers(multiple) and another server
will become the subscriber.

I just curious to know, we can achieve better throughput only with
publish-subscribe messaging pattern.

Couple of other things,
1) I did not understand quite why messages are getting dropped in case of
publish subscribe model. I am using synchronization sockets here.
2) In all messaging pattern, the queue exists on the side where it binds
the socket, is it correct?

On 31 August 2012 19:51, Wolfgang Richter <wolf at cs.cmu.edu> wrote:

> It sounds like you could easily do this with a publish-subscribe
> architecture?
>
> Do you care if some messages are dropped?
>
> --
> Wolf
>
> On Fri, Aug 31, 2012 at 12:37 AM, girish kumar <girishbangaram at gmail.com>
> wrote:
> > Hi All,
> >
> > I really appreciate if any body solved these type of scenarios.
> >
> > Thanks in advance.
> >
> >
> > On 29 August 2012 22:26, girish kumar <girishbangaram at gmail.com> wrote:
> >>
> >> Hi All,
> >>
> >> I am looking for a messaging pattern for the following scenario.
> >>
> >> I have a Java NIO based server X, which has some threads processing
> client
> >> requests. These threads receive events asynchronously. Now, I want to
> send
> >> some of the events to another service(another server) Y in asynchronous
> >> fashion.
> >>
> >> Please suggest me a scalable messaging pattern for the above scenario.
> >>
> >> --
> >> With Best Regards,
> >> Girish
> >>
> >
> >
> >
> > --
> > With Best Regards,
> > Girish
> >
> >
> > _______________________________________________
> > zeromq-dev mailing list
> > zeromq-dev at lists.zeromq.org
> > http://lists.zeromq.org/mailman/listinfo/zeromq-dev
> >
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>



-- 
With Best Regards,
Girish
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20120901/ca809dac/attachment.htm>