[rabbitmq-discuss] Recommended queue architecture

Alvaro Videla videlalvaro at gmail.com
Thu Dec 19 11:34:14 GMT 2013


RabbitMQ won't do any aggregation for you. What you could do is route
similar messages to the same queue(s). Also AMQP messages can have a
correlation_id property that you could use to aggregate them later.



On Thu, Dec 19, 2013 at 2:31 AM, Mike Nibeck <mnibeck at gmail.com> wrote:
> Scenario: Order processing system. Orders can contain multiple children
> objects (items, addresses, customer, etc.) We place messages on a queue when
> any elements of an order gets modified. We want to be able to correlate all
> of the messages into a single message "Order Updated", with the details of
> what got updated. The individual edits can come in at any time, and not
> necessarily all of the edits for given order will be processed at the same
> time.
> In this scenario, I feel that we ned to somehow persist all of these
> messages and then do some sort of data analysis and group all of the related
> messages for a specific order. Can any of this aggregation occur within the
> queuing system, or will we need to persist these messages in another data
> store (DB) and process on a schedule?
> _mike
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list