Windows Workflow的开放替代品 [英] Open alternatives to Windows Workflow
问题描述
预警:还有其他一些与此类似的问题，但并没有完全回答该问题(这些问题包括:有人可以推荐Windows Workflow的.Net开源替代品吗?)
Pre-warning: There are some other questions similar to this but don't quite answer the question (these include: Alternatives to Windows Workflow Foundation?, Can anyone recommend a .Net open source alternative to Windows Workflow?)
我们正在开发一个基于事件的状态机系统，目前正在研究Windows工作流，我们的系统在响应多种来源(xmpp，http，sms，电话，电子邮件等)进入系统，具有可扩展性和弹性，最重要的是可定制的.由于各种原因(和尽职调查)，我正在寻找支持类似于Windows Workflow Foundation(以及更多-如果可能的话)的功能的开放式工作流引擎，主要是(但如果有一些引擎不支持，则没有太大关系).不支持某些功能):
We are developing a system that is an event based state machine, currently we are investigating windows workflow, our system needs to be low latency in its response to events from a multitude of sources (xmpp, http, sms, phone call, email etc etc) coming into the system, scalable and resilient and most importantly customisable. For a variety of reasons (and due diligence) I am looking for open workflow engines that support functions similar to Windows Workflow Foundation (and more - if possible), mainly (but it doesn't matter too much if there are engines that don't support some features):
- 长期运行的任务的持久性以及在外部事件上恢复任务
- 高性能，低延迟
- 制定自定义动作的能力
- 动态指定工作流程的能力
- 跟踪和追踪
我不受平台或语言的束缚，我希望获得你们的帮助和提示，以便我可以开始更仔细地研究引擎以及您使用引擎的任何经验.
I am not constrained to platform or language, and I would love some help and tips from you guys so that I can start to investigate the engines more closely and any experiences you had with the engines.
保罗.
推荐答案
"Java端":
Apache ODE(业务流程导向器引擎)执行遵循WS-BPEL标准编写的业务流程.它与Web服务进行通信，发送和接收消息，处理数据操作和错误恢复(如流程定义所描述).它支持长期和短期生命周期执行，以协调应用程序中所有的服务.
"Java side":
Apache ODE (Orchestration Director Engine) executes business processes written following the WS-BPEL standard. It talks to web services, sending and receiving messages, handling data manipulation and error recovery as described by your process definition. It supports both long and short living process executions to orchestrate all the services that are part of your application.
OSWorkflow可以被视为低级"工作流实施.在其他工作流程系统中可能由图形图标表示的诸如循环"和条件"之类的情况必须在OSWorkflow中进行编码".
OSWorkflow can be considered a "low level" workflow implementation. Situations like "loops" and "conditions" that might be represented by a graphical icon in other workflow systems must be "coded" in OSWorkflow.
Shark是可扩展的工作流引擎框架，包括完全基于WfMC规范的标准实现，使用XPDL(无任何专有扩展名！)作为其本机工作流过程定义格式，以及用于在服务器端执行系统活动的WfMC"ToolAgents" API.
Shark is an extendable workflow engine framework including a standard implementation completely based on WfMC specifications using XPDL (without any proprietary extensions !) as its native workflow process definition format and the WfMC "ToolAgents" API for serverside execution of system activitie
Python方面: http://bika.sourceforge.net/ http://www.vivtek.com/wftk/ 我会为您提供帮助的:-)
Python side: http://bika.sourceforge.net/ http://www.vivtek.com/wftk/ I this will help you :-)
这篇关于Windows Workflow的开放替代品的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
