选择哪个工作流引擎? [英] Which workflow engine to choose?
问题描述
我们目前正在评估 BPM 引擎，我非常感谢社区的投入.我正在做自己的尽职调查，但也想听听基于实施案例的建议.
We are currently in the process of evaluating a BPM engine and I'd really appreciate the community input. I am doing my own due diligence but would also like to hear on the suggestion based on implementation stories.
我的主要评价标准如下
- 开源和 OEM 友好许可
- 生产装置(成功案例有很大帮助)
- 提供商业支持
- 开放标准支持 - BPMN
- 根据输入动态创建/组装工作流
- 可嵌入
目前我正在评估 Activiti 和 JBPM.Bonita 开放式 BPM 似乎也是一个不错的选择，但从未使用过.你们在 Bonita 上有成功的部署吗?
Currently I am evaluating Activiti and JBPM. Bonita open BPM seems like a good candidate as well but never used it. Do you guys have any successful deployments on Bonita?
推荐答案
我刚刚做了一个 Activiti 与 jBPM 的评估.
I've just been doing an evaluation of Activiti vs jBPM.
事实上，这两种解决方案之间的差距似乎很小.
In fact there seems to be very little between the two solutions.
- Activiti 是 Apache V2，jBPM 5.0 也是 Apache V2.
- 我们目前正在使用 Activiti，但该项目仍处于开发阶段，因此我无法评论其在生产中的稳健性.
- jBPM 正在开始产品化过程，因此将在 2012 年第一季度提供对 5.x 的支持，请参见幻灯片 32:jBPM 演示.Redhat 不支持 jBPM 4.
- jBPM 4.x 不支持 BPMN 2.0，但 5.x 支持，Activiti 也支持.jBPM 5.0 刚刚发布，其中包括对 BPMN 2.0 的支持.所以现在两个解决方案都支持 BPMN 2.0.
- 我不太清楚您的意思，但是您可以通过这两个 API 做很多事情
- 同样，不确定您的意思，您的意思是作为应用服务器的一部分嵌入，在这种情况下，两种解决方案都是.
- Activiti is Apache V2, jBPM 5.0 is also Apache V2.
- We're currently using Activiti, but the project is still in dev, so I can't comment on its robustness in production.
- jBPM is beginning the productization process, so support for 5.x will be available in Q1 2012, see slide 32: jBPM demo. jBPM 4 was not supported by Redhat.
- jBPM 4.x did not support BPMN 2.0, but 5.x does, Activiti does as well. jBPM 5.0 has just been released, which includes support for BPMN 2.0. So now both solutions support BPMN 2.0.
- I'm not quite sure what you mean by this, but you can do a lot through both APIs
- Again, not sure what you mean by this, do you mean embedded as part of an application server, in which case, yes for both solutions.
我们对 jBPM 的标准之一是与 Guvnor 的交互，当我下载并运行 jBPM 的演示安装 (28/03/2011) 时，似乎仍然存在一些主要错误 (GUVNOR-1274)，所以我个人会在选择采用此解决方案之前进行更多测试.
One of our criteria for jBPM was the interaction with Guvnor, and when I downloaded and ran the demo install for jBPM (28/03/2011) and there still seemed to be some major bugs (GUVNOR-1274), so I personally would test a lot more before I chose to pursue this solution.
事实上，我们会推荐上述两种解决方案中的一种，但我们还不确定哪个，我们将在今年晚些时候更仔细地研究.
In fact, we will be recommending one of the above two solutions, but we're not sure which yet, we'll look at it more closely later this year.
这篇关于选择哪个工作流引擎?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
