[erlang-questions] Re: A discussion in application design and event propagation

[Fred Hebert]

On Mon, Apr 19, 2010 at 12:14 PM, Garrett Smith <g@REDACTED> wrote:

>
>
> Thinking in architectural terms, this strikes me as a pub/sub problem
> that a message broker would handle well. RabbitMQ (AMQP), e.g., would
> let you publish events to an exchange, which can then be routed to
> various queues via bindings. RabbitMQ in particular is a nice option
> for Erlang developers.
>
> Garrett
>
> ________________________________________________________________
> erlang-questions (at) erlang.org mailing list.
> See http://www.erlang.org/faq.html
> To unsubscribe; mailto:erlang-questions-unsubscribe@REDACTED
>
>
I'm not too familiar with RabbitMQ and queue usage past using them to send
the load from an application's frontend to a backend (and also surviving
huge peaks in users).

How well does it lend itself to real-time applications? How would you make
it work with N tables and 4N users? From my little experience with queuing
systems like this, it sounds like the number of queues or topics required
would be huge, otherwise the amount of filtering even higher. What's your
take on that?