[rabbitmq-discuss] Suggestion - Simple Pub/Sub

[Aamir Khan]

There will be many users and topics. For simplicity lets call users as U1,
U2, U3 and topic as T1, T2. Now any user can publish and subscribe to any
topic after authentication mechanism. So, what i understood by examples is
that i should create create queues for each (user,topic) combination. In
exchange we write the logic if the message is to be sent to T1 then all the
queues with T1 as topic should get that message. Am i on correct path ?

On Wed, Jan 11, 2012 at 9:34 PM, Alexis Richardson <alexis at rabbitmq.com>wrote:

> Aamir
>
> You can do 1 using RabbitMQ, because it lets you combine pubsub with
> durable buffers (aka "queues").
>
> You can do 2 by adding an archiving process as a subscriber to the
> firehose.
>
> alexis
>
>
> On Wed, Jan 11, 2012 at 4:00 PM, Aamir Khan <ak4u2009 at gmail.com> wrote:
> > Well, There are two situations for the application.
> >
> > 1. When there is a live QA session going on, so everybody can ask
> question
> > and we have to just push the questions to all the subscribers using the
> > messaging middle ware. In case we are getting questions at a very high
> > frequency then we will have a buffer and send questions to subscribers
> after
> > certain period of time in order to avoid the confusion because of too
> much
> > questions.
> >
> > 2. There is no live session going on and you can't ask any question, but
> can
> > just browse through the talk that happened in the past.
> >
> > I hope i have mentioned clearly what i am trying to build. Please give
> your
> > valuable suggestions how should i go about it ?
> >
> >
> > On Wed, Jan 11, 2012 at 9:13 PM, Alexis Richardson <alexis at rabbitmq.com>
> > wrote:
> >>
> >> What kind of storage do you want to use, and for what use cases?
> >>
> >> On Wed, Jan 11, 2012 at 3:27 PM, Aamir Khan <ak4u2009 at gmail.com> wrote:
> >> > Hi,
> >> >
> >> > I am working on a web application in which lots of users can send
> >> > message to
> >> > a central server. This central server will push message to all the
> users
> >> > based on topic based filtering. This can be easily accomplished by
> using
> >> > rabbitMQ. I am using Tornado web server for non blocking
> asynchronously
> >> > pushing the messages to clients with rabbitMQ as middle ware for the
> >> > message
> >> > queuing. My point lies in that i also need to store each message into
> >> > database so as to keep record of each. Since the messages won't be
> very
> >> > structured data so i am planning to have noSQL storage. Can somebody
> >> > please
> >> > suggest some documentation where rabbitMQ is used in addition to
> >> > database
> >> > storage ?
> >> >
> >> > Well, i also read that i can use Redis Pub/Sub to have this feature of
> >> > subscribe and publish model, so i am quite confused whether to go for
> >> > rabbitMQ ?
> >> >
> >> > Any suggestions are most welcome.
> >> >
> >> >
> >> > --
> >> > Aamir Khan | 3rd Year  | Computer Science & Engineering | IIT Roorkee
> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > rabbitmq-discuss mailing list
> >> > rabbitmq-discuss at lists.rabbitmq.com
> >> > https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
> >> >
> >
> >
> >
> >
> > --
> > Aamir Khan | 3rd Year  | Computer Science & Engineering | IIT Roorkee
> >
> >
>



-- 
Aamir Khan | 3rd Year  | Computer Science & Engineering | IIT Roorkee
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120111/0c09affc/attachment.htm>