java jBPM 会死吗？jBPM 和 Activiti BPMN 的未来是什么？

Is jBPM dying? What is the future of jBPM and Activiti BPMN?

提问by Javatar

I have heard that the developers of "jBPM" have transferred to "Activiti BPMN 2" in recent times (ex: Tom).

我听说“jBPM”的开发者最近已经转移到“Activiti BPMN 2”（例如：Tom）。

I am wondering about is whether the support for jBPM will be over or not.. Besides, I would be glad to hear your ideas about if the improvements of Activiti BPMN will make it better or useful than jBPM as time goes on?

我想知道对 jBPM 的支持是否会结束。此外，我很高兴听到您关于 Activiti BPMN 的改进是否会随着时间的推移使其比 jBPM 更好或有用的想法？

I would also like to know what are the pros/cons between them.

我也想知道它们之间的优缺点是什么。

采纳答案by Andreas Kuckartz

Activiti is an interesting project for several reasons:

Activiti 是一个有趣的项目，原因如下：

1. They intend to commoditize the engine. For that reason they use the Apache Software License. So far several companies are backing that project. The "business model" is somewhat similar to that used by OpenStack.

2. It makes sense to have one BPMN 2.0 engine which is used and can be used by everybody. This does include jBoss (but I doubt that they will switch soon).

1. 他们打算将发动机商品化。出于这个原因，他们使用 Apache 软件许可证。到目前为止，有几家公司正在支持该项目。“商业模式”有点类似于 OpenStack 使用的模式。

2. 拥有一个所有人都可以使用的 BPMN 2.0 引擎是有意义的。这确实包括 jBoss（但我怀疑他们会很快切换）。

回答by Marco

Please check out jBPM 7: https://www.jbpm.org/learn/releases.html

请查看 jBPM 7：https: //www.jbpm.org/learn/releases.html

Support for and development of jBPM is definitely still ongoing!

对 jBPM 的支持和开发肯定还在进行中！

(Btw, jBPM also uses BPMN 2.0)

（顺便说一句，jBPM 也使用 BPMN 2.0）

回答by Dhaval Shah

jBPM and Activiti Both are BPMN engines But on Comparing both of them

jBPM 和 Activiti 都是 BPMN 引擎但是比较两者

• jBPM is more complex then Activiti

• it is really easy to integrate with Activiti as compared to jBPM

• jBPM 比 Activiti 更复杂

• 与 jBPM 相比，与 Activiti 集成真的很容易

but still jbpm is under development phase so is activity

但 jbpm 仍处于开发阶段，活动也是如此

Whatever is your requirement, everything is available in jbpm ,it is very good BPM but as compared to Activity it is bit complex and not so fruitful.

无论您的要求是什么，jbpm 中的所有内容都可以使用，它是非常好的 BPM，但与 Activity 相比，它有点复杂，而且效果不佳。

So if you are yet to decide which bpm I would suggest you to go for Activity because integration of anything with Activity say LDAP or Spring is preety easier as compared to JBPM.

因此，如果您尚未决定使用哪种 bpm，我建议您使用 Activity，因为与 JBPM 相比，任何与 Activity 的集成都说 LDAP 或 Spring 更容易。

Also you can easily learn Activity because of good userguide and documentation provided by community, but in case of JBPM userguide as well as documentation neither are so helpful. Also Developer guide book is also not up to the mark.

由于社区提供的良好用户指南和文档，您也可以轻松学习 Activity，但在 JBPM 用户指南和文档的情况下，两者都没有太大帮助。此外，开发人员指南也不符合标准。

Well ball is in your court ,you have to take decision.

那么球在你的球场上，你必须做出决定。

All the Best.

一切顺利。

chk this Link

chk这个链接

http://www.mastertheboss.com/activiti-bpmn/jbpm-vs-activiti-which-to-choose

http://www.mastertheboss.com/activiti-bpmn/jbpm-vs-activiti-which-to-choose

回答by Francesco

Well jBPM is surely not dying although there's a strong departure from the 3.x and 4.x releases. here, you can read more about jBPM and ActivitiCheers Francesco

jBPM 肯定不会消亡，尽管与 3.x 和 4.x 版本有很大的不同。在这里，您可以阅读有关jBPM 和 ActivitiCheers Francesco 的更多信息

回答by user3366231

jBPM has traditionally had one big drawback; usability. Has always been very powerful, but the hardest to use and integrate with, a major reason in Activiti's popularity and jBPMs decline in usage.

jBPM 传统上有一个很大的缺点；可用性。一直很强大，但最难使用和集成，这是 Activiti 流行和 jBPM 使用率下降的主要原因。

However, this year sees the resurgence of jBPM with the new Version 6 rolled out as well as the release of the Wira platform ( http://www.a1.io/a1io_blog/wira-for-jbpm/)that provides a really good jBPM execution framework.

然而，今年随着新版本 6 的推出以及 Wira 平台 ( http://www.a1.io/a1io_blog/wira-for-jbpm/)的发布，jBPM 重新兴起，它提供了一个非常好的jBPM 执行框架。

回答by rob2universe

I withdrew my previous answer from '14. From today's perspective the answer should certainly include jBPM, Activiti, Flowable and Camunda. This is the selection one ends up with when looking for the significant BPMN2 standard-based open-source workflow engines.

我从 14 年撤回了我之前的回答。从今天的角度来看，答案当然应该包括 jBPM、Activiti、Flowable 和 Camunda。这是在寻找重要的基于 BPMN2 标准的开源工作流引擎时的选择。

IMHO, jBPM remains very Java-centric, feels like an old-school open-source product built by a community and still shows a lack of product management.

恕我直言，jBPM 仍然非常以 Java 为中心，感觉就像一个由社区构建的老式开源产品，仍然缺乏产品管理。

Major parts of the Activiti contributors lefts and forked Camunda and Flowable. It seems like Activiti's focus is around the needs of Alfresco and their DMS.

Activiti 贡献者的主要部分离开并分叉了 Camunda 和 Flowable。似乎 Activiti 的重点是围绕 Alfresco 及其 DMS 的需求。

If you consider Google trends of relevance to the answer, it currently looks like this: https://trends.google.com/trends/explore?q=jBPM,Camunda,Activiti,Flowable

如果您考虑与答案相关的 Google 趋势，它目前看起来像这样：https: //trends.google.com/trends/explore?q=jBPM,Camunda,Activiti, Flowable

回答by Ayman Arif

History Lesson:

历史课：

jBPM and its resultant projects:

jBPM 及其产生的项目：

1. jBPMis created at Redhat as a workflow engine adhering to BPMN 2.0 specification
2. Creators of jBPM leave jBPM project and Redhat to join Alfresco. There they create, Activi.

3. Creators of Activi leave Alfresco and start a new BPM tool, Flowable, which is a fork from Activi.

4. Camundais another BPM tool forked from Activi. They also adhere to BPMN 2.0 Specification. They have Zeebe, a cloud-native BPM with connectors to Java, gRPC, Elasticsearch and Kubernetes.

1. jBPM是在 Redhat 创建的，作为遵循 BPMN 2.0 规范的工作流引擎
2. jBPM 的创建者离开 jBPM 项目和 Redhat 加入 Alfresco。他们在那里创建，Activi。

3. Acti 的创建者离开 Alfresco 并开始了一个新的 BPM 工具Flowable，它是来自 Acti 的一个分支。

4. Camunda是另一个从Activi 衍生出来的BPM 工具。他们还遵守 BPMN 2.0 规范。他们有 Zeebe，这是一个云原生 BPM，带有到 Java、gRPC、Elasticsearch 和 Kubernetes 的连接器。

Non-jBPM workflow/orchestration tools:

非 jBPM 工作流/编排工具：

1. Uber cadence
2. Apache Airflow
3. Netflix Conductor: Microservice workflow orchestration engine.

1. 优步节奏
2. 阿帕奇气流
3. Netflix Conductor：微服务工作流编排引擎。

回答by user674479

As I understand it, jBPM 5is drools flowwhich just got renamed. So it started as being part of the drools business rules engine,and is now the successor of jBPM 4. So i dont think it really matters that the jBPM project lead moved to activiti...

据我了解，jBPM 5是刚刚重命名的流口水。所以它开始是作为 drools 业务规则引擎的一部分，现在是jBPM 4的继承者。所以我认为 jBPM 项目负责人转向活动并不重要......