最近我们有个使用了jbpm 6.2的批处理模块，因为大BOSS一直觉得太重了，希望有更加轻量级的解决方案，因为我们基本上没有真正意义上流程的概念，只有静态的流程图，因为一直忙于其他事情，于是这周才正式开始研究jbpm的一些细节（前几年很多支持的项目中也接触过，不过更多的是解决一些故障类问题，本身对流程类的不感冒）。顺便研究了下jbpm 6 vs activities 5（不过activities是jbpm之后创始人分道扬镳新搞的，这个很早就知道了，跟mysql和mariadb一样）：
jBPM 6
jBPM 6 is the latest community version of the jBPM project. It is based on the
BPMN 2.0 specification and supports the entire life cycle of the business process (from authoring through execution to monitoring and management).
It offers open-source business process execution and management, including
- Embeddable, lightweight Java process engine, supporting native BPMN 2.0 execution
- human interaction using an independent WS-HT task service
- BPMN 2.0 process modeling in Eclipse (developers) and the web (business users)
- web tooling to model, deploy, execute and monitor your processes, including for example a data and form modeler, simulation, deployment, task lists, etc.
- web-based business activity monitoring and reporting that allows you to define your own reports
- managing and deploying your processes using technologies underneath like Git and Maven
- an execution server that you can remotely connect to (REST, JMS) and can be deployed in a clustered environment for load balancing and high availability
- tight, powerful integration with business rules and event processing
Activiti
Activiti 5.15.0 is the latest community version of the Activiti project. It's a Java process engine that runs BPMN 2 processes natively. It will have the following key properties:
- Allows user updates to be combined with process updates in a single transaction
- Runs on any Java environment like Spring, JTA, standalone with any form of transaction demarcation.
- Easy to get up and running with the setup utility
- Built to support the cloud scalability from the ground up
- Very simple to add new custom activity types and complete dedicated process languages
- Rock solid
- Extremely fast
- Transactional timers
- Asynchronous continuations
- Hidden event listeners for decoupling software technical details from business level diagram
- Ability to test process executions in isolation in a plain unit test
I have referred few articles and given below are the differences between jBPM and Activiti:
|
Description
|
Activiti
|
jBPM
|
|
Community members
|
Activiti has a base team consisting of
Alfresco employees. In addition,
companies like SpringSource,
FuseSource and MuleSoft provide
resources on specific components. And of course, there are individual open source developers committing to the Activiti project.
|
jBPM has a base team of JBoss
employees. In addition there are individual committers.
|
|
Spring support
|
Activiti has native Spring support, which makes it very easy use Spring beans in your processes and use Spring for JPA and transaction management.
|
jBPM has no native Spring
support, but you can use Spring
with additional development effort.
|
|
Business rules support
|
Activiti provides a basic integration with the Drools rule engine to support the BPMN 2.0 business rule task.
|
jBPM and Drools are integrated on a project level and therefore there’s native integration with Drools on various levels.
|
|
Additional tools
|
Activiti provides a modeler (Oryx) and designer (Eclipse) tool to model new process definitions. But the main differentiator is the Activiti Explorer, which provides an easy-to-use web interface to start new processes, work with tasks and forms and manage the running processes. In addition it provides ad-hoc task support and collaboration functionality.
|
jBPM also provides a modeler
based on the Oryx project and a Eclipse designer. With a web
application you can start new
process instances and work with tasks. The form support is
limited
|
|
Project
|
Activiti has a strong developer and user community with a solid release schedule of 2 months. Its main components are the Engine, Designer, Explorer and REST application
|
jBPM has a strong developer and user community. The release schedule is not crystal clear and some releases have been postponed a couple of times. The Designer application is (at the moment of writing) still based on Drools Flow and the promised new Eclipse plug-in keeps getting postponed
|
其他特性还没有仔细研究，后面会把我们实际用到的表使用以及重要性都梳理出来并更新。