<div dir="ltr">Another off the wall idea - create a queue for "message orders received/completed", publish on the first order "started order id", and then create a queue for each "order id". Then you could start up a listener on that "message orders received/completed" to dynamically start listeners on the specific "order id" queue and shut it down after the queue is completed. Not sure this is really a good idea though<div>
<br></div><div>Jason</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Dec 19, 2013 at 5:34 AM, Alvaro Videla <span dir="ltr"><<a href="mailto:videlalvaro@gmail.com" target="_blank">videlalvaro@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
RabbitMQ won't do any aggregation for you. What you could do is route<br>
similar messages to the same queue(s). Also AMQP messages can have a<br>
correlation_id property that you could use to aggregate them later.<br>
<br>
Regards,<br>
<br>
Alvaro<br>
<div><div class="h5"><br>
On Thu, Dec 19, 2013 at 2:31 AM, Mike Nibeck <<a href="mailto:mnibeck@gmail.com">mnibeck@gmail.com</a>> wrote:<br>
> Scenario: Order processing system. Orders can contain multiple children<br>
> objects (items, addresses, customer, etc.) We place messages on a queue when<br>
> any elements of an order gets modified. We want to be able to correlate all<br>
> of the messages into a single message "Order Updated", with the details of<br>
> what got updated. The individual edits can come in at any time, and not<br>
> necessarily all of the edits for given order will be processed at the same<br>
> time.<br>
><br>
> In this scenario, I feel that we ned to somehow persist all of these<br>
> messages and then do some sort of data analysis and group all of the related<br>
> messages for a specific order. Can any of this aggregation occur within the<br>
> queuing system, or will we need to persist these messages in another data<br>
> store (DB) and process on a schedule?<br>
><br>
> _mike<br>
><br>
><br>
</div></div>> _______________________________________________<br>
> rabbitmq-discuss mailing list<br>
> <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
> <a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
><br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Jason McIntosh<br><a href="https://github.com/jasonmcintosh/" target="_blank">https://github.com/jasonmcintosh/</a><br>573-424-7612</div>
</div>