适用于Java的轻量级工作流引擎 [英] Lightweight workflow engine for Java

查看:301
本文介绍了适用于Java的轻量级工作流引擎的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

编写新的工作流引擎或使用现有的BPM引擎是否更好:jBPM 5,Activiti 5?

Is it better to write a new workflow engine or to use an existing BPM engine: jBPM 5, Activiti 5?

我的应用程序是基于Web的应用程序和性能很重要我怀疑的是,与编写简单的工作流引擎相比,使用jBPM / Activiti是否会带来性能开销。

My application is a web based application and performance is important. My doubt is whether using jBPM/Activiti will be a performance overhead compared to writing a simple workflow engine.

如果我选择自我实现,我将错过工作流的可视化。为了表现,它可以交易。

If I go with self implementation, I will miss visualization of workflow. For performance it can be traded.

推荐答案

这实际上取决于您的要求。首先,看看你是否真的需要工作流引擎(或其他来源)。除非你真的需要它,否则你应该避免它。

This really depends on your requirements. First, see if you really need a workflow engine (this or other sources). Unless you really need it, probably you should avoid it.

如果你真的需要提供工作流引擎的东西,我会选择一个已经构建的工具。使用jbpm或activiti的人在构建工作流引擎方面拥有的经验比你更多,因此可能已经调整以提高性能。

If you really need what provides a workflow engine, I would pick one that is already built. People who works with jbpm or activiti have much more experience than you in building workflow engines, so it is probably already tunned to improve performance.

这篇关于适用于Java的轻量级工作流引擎的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆