<div dir="ltr">I've used Camel before. Mixed bag of likes and dislikes.<div><br></div><div>I don't know of any Erlang-specific ESB packages, though, really, do you need more than just an FSM? Define one gen_fsm per flow and let those run themselves through your service pools. </div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Mar 12, 2014 at 8:15 PM, Suraj Kumar <span dir="ltr"><<a href="mailto:suraj.kumar@inmobi.com" target="_blank">suraj.kumar@inmobi.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>I'm on the lookout for a solid workflow execution engine. The idea is to make that engine consume data from our CouchDB database and maintain computed workflow states back in the same highly available data store.</div>
<div><br></div><div>The current contender is JBPM. JBPM makes people feel very secure ("Enterprise-grade solution", XML and BPMN and BPEL and what not :) ). But really, it is because there are many tools to make development, testing and monitoring of workflows easy. </div>
<div> </div><div>A native erlang solution, like WEE, could be of help: <a href="http://sourceforge.net/projects/weeworkflow/" target="_blank">http://sourceforge.net/projects/weeworkflow/</a> But I'm afraid, it will still be more effort to setup WEE for the purpose of:</div>
<div><ul><li>Modeling many workflows easily</li><li>Validating defined workflows</li><li>monitor state of execution of all workflows across all entities</li></ul></div><div><br></div><div>Any suggestions or pointers to how to pull this off? <span class="HOEnZb"><font color="#888888"><br clear="all">
<div><br></div>-- <br><div dir="ltr">An Onion is the Onion skin and the Onion under the skin until the Onion Skin without any Onion underneath.<div><br></div></div>
</font></span></div></div><span class="HOEnZb"><font color="#888888">
<br>
<div><span style="font-family:Arial">______________________________<u></u>______________________________<u></u>_</span></div><span style="font-family:Arial"><font color="#808080">The information contained in this communication is intended solely for the use of the individual or entity to whom it is addressed and others authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. The firm is neither liable for the proper and complete transmission of the information contained in this communication nor for any delay in its receipt.</font></span></font></span><br>
_______________________________________________<br>
erlang-questions mailing list<br>
<a href="mailto:erlang-questions@erlang.org">erlang-questions@erlang.org</a><br>
<a href="http://erlang.org/mailman/listinfo/erlang-questions" target="_blank">http://erlang.org/mailman/listinfo/erlang-questions</a><br>
<br></blockquote></div><br></div>