[rabbitmq-discuss] Exchanges and queues for a social design system

[Emile Joubert]

Hi,

It is not possible to say what the "right" approach is. An alternative
design is to create a common exchange and one queue for each user, with
bindings for all messages that a user is interested in. Messages will be
routed to the user's queue based on the bindings.


-Emile




On 24/09/13 11:10, tyger2007 at yahoo.com wrote:
> Thanks Michael for your response , however I have another question ,
> rabbit is best for propagation and routing and is not a database  , I am
> designing a social based system and I have my users in the database .
> e.g Jack follows john , john follows jack
> So when jack makes a post I write the post to my db and deliver the
> message to john by writing to johns exchange .John gets the message by
> waiting on a queue based on any message written to his exchange.is this
> the right approach to designing a social system with rabbitmq ?, thanks.




> Date: Mon, 23 Sep 2013 10:56:39 +0100
> From: Michael Klishin <michael.s.klishin at gmail.com>
> Subject: Re: [rabbitmq-discuss] consumer in background
> To: Discussions about RabbitMQ <rabbitmq-discuss at lists.rabbitmq.com>
> Message-ID:
> <CAE3HoVTd6rw8t0y9EwqxaNftLCno_4ZtSHRCDuYfOB+1QwO=Pw at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
> 
> 2013/9/23 tyger2007 at yahoo.com <tyger2007 at yahoo.com>
> 
>> Thanks alvaro like I said this concept is totally new to me , however I
>> would like to know if the consumers would run stand alone , that is apart
>> from the web server ? ,
> 
> 
> Yes. PHP environment is reset between requests, this does not work very
> well with
> long-running network connections.
> 
> 
>> if that is the case does it mean I would have to keep my command line open
>> always on my servers?
> 
> 
> Just run the process in the background (daemonized).
> -- 
> MK
> 
> http://github.com/michaelklishin
> http://twitter.com/michaelklishin