is RabbitMQ suitable for 'chaining' or sequential tasks?

[Gallagher Polyn]

Hi,

I'm experimenting with RabbitMQ (AMQP) by using it to handle sequential chains of background tasks. Tasks include comparing data from datastores, updating items, making external API calls, etc. Units of work may follow different paths through a branching structure I am constructing with RabbitMQ.

Meanwhile, most AMQP examples I've seen, including the RabbitMQ tutorials, describe tasks at one level of depth.

The difference between official examples and my experimentation concerns me that I am misusing AMQP. So, my question:

Is it preferable to combine all operations in independent tasks, keeping RabbitMQ utilization one-level deep, or is it just as well that tasks be chained in RabbitMQ?

Thank you for any comment,

Gallagher 

[Michael Klishin]

Multiple projects use RabbitMQ for "background tasks." RabbitMQ is not aware of said tasks' dependencies or grouping, feel free to use it however you see fit. Data pipelines are common these days, using RabbitMQ or something else.

MK

--
You received this message because you are subscribed to the Google Groups "rabbitmq-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rabbitmq-user...@googlegroups.com.
To post to this group, send email to rabbitm...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Michael Klishin]

On 9 May 2015 at 14:11:56, Gallagher Polyn (gallagh...@gmail.com) wrote:
> Tasks include comparing data from datastores, updating items,
> making external API calls, etc. Units of work may follow different
> paths through a branching structure I am constructing with RabbitMQ.

Note that there are existing projects, including those supporting RabbitMQ
for the messaging layer, that can help you avoid re-inventing the wheel.

Spring XD is one I'd recommend taking a look at:
http://projects.spring.io/spring-xd/ 
--
MK

Staff Software Engineer, Pivotal/RabbitMQ