[erlang-questions] Workflow Execution Engine and DSL documentation

Suraj Kumar suraj.kumar@REDACTED
Thu Mar 13 04:15:55 CET 2014


Hi,

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.

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.

A native erlang solution, like WEE, could be of help:
http://sourceforge.net/projects/weeworkflow/ But I'm afraid, it will still
be more effort to setup WEE for the purpose of:

   - Modeling many workflows easily
   - Validating defined workflows
   - monitor state of execution of all workflows across all entities


Any suggestions or pointers to how to pull this off?

-- 
An Onion is the Onion skin and the Onion under the skin until the Onion
Skin without any Onion underneath.

-- 
_____________________________________________________________
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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140313/3d49afd3/attachment.htm>


More information about the erlang-questions mailing list