[erlang-questions] design pattern question for messaging

[Ryan Brown]

Two more cents. I work on the same system as Rich and I can see a hybrid
approach here being a very nice way to go. You could use rabbit (or really
any MQ of your choice) for persistence with one queue per step in the
process. Your application would then just listen to messages from each
queue, spin a process to handle it and enqueue it in the next step. As
Jesper mentioned, this could all be tracked nicely via an fsm.

Miles, do you feel like your questions have been answered for this thread?
I know it has spawned some creative thoughts on my end!

-- 
-rb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140723/a91b5190/attachment.htm>