[rabbitmq-discuss] Orchestration vs. Choreography

[Isaias Barroso]

Dear all,

I'm design a process that is splitted on some tasks (one queue for each
piece of process). To a sample, suppose I have a message that can treated
for many steps: Retrieve Information, enrich information, Save on Database,
but each step can occurs or not, so I've thought about on two approaches :

1 - Orchestration: In this case a central component will receive the
message and decide for each step, after execution of each step this
component will decide the next step.
2 - Choreography: In this case each step must to know the next step and
send message for next queue

Does anybody has some opinion about the better approach? Does anybody knows
some tool/framework that works top of Rabbit that manage it (Java if
possible) ?


Best regards


-- 
Isaías Barroso
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120107/1cc8bf5b/attachment.htm>