Camel 与 BPM 中的工作流程 [英] Work Flow in Camel vs BPM

问题描述

我们使用 Apache camel 作为工作流引擎.首先我们有 WebService One 并等待响应，并基于响应调用 WebService 2 或 WebService 3.它是一个纯工作流，有几个像这样的工作流步骤.我有在 BPM 产品上工作的机会较少，例如 JBOSS BPM 等.除了长期运行和支持人工任务之外，我们还有什么其他好的理由必须选择 BPM 产品?如果我们的项目不需要长时间运行和人工任务支持，我们可以使用 Camel 或 JBOSS FUSE 来编排业务流程吗?

We have used Apache camel as a Workflow engine.First Wehave WebService One and wait for the response and based on the response call WebService 2 or WebService 3.Its a pure WorkFlow and have couple of WorkFlow Steps like this.I have got less chances to work on a BPM product , like JBOSS BPM etc. Other than long running and support for human task any other good reason we have to choose a BPM product ? If both long running and human task support are not needed in our project can we use Camel or JBOSS FUSE to orchestrate business processes ?

谢谢，狮子座.

推荐答案

是的.. 正如 Antoine 提到的，从技术角度来看，这听起来可能很相似，但如果您使用 Camel 作为状态机来移动数据，您就不会这样做根本没有 BPM，你离 BPM 太远了.

Yeah.. as Antoine mention, from the technical perspective it might sounds similar, but if you are using Camel as a state machine to move data you are not doing BPM at all, you are extremely far away for BPM.

BPM 在一个简单的状态机之上添加了更多内容.仅从您用于对业务场景建模的语言开始，再到随 BPM 一起提供的工具，如果您只使用骆驼，您将失去很多.我可以从技术角度理解您的问题，但从更广泛的公司角度来看，您无法比较解决方案.

BPM adds a lot more on top of just a simple state machine. Just starting from the language that you use to model business scenarios to the tooling that is provided along with a BPM you will be loosing a lot if you just use camel. I can understand your question from a technical point of view, but from a more company wide perspective you cannot compare solutions.

我认为你需要问自己以下问题:

I think that you need to ask yourself the following questions:

1) 您是否有兴趣与非技术人员分享哪些 Web 服务(此时您的骆驼路线)被调用?

1) Are you going to be interested in sharing which web services (your camel routes at this point) are called with non technical people?

2) 您是否有兴趣获取审核日志和仪表板之类的屏幕，以分析您为做出业务决策而调用的服务的情况?

2) are you going to be interested in getting audit logs and dashboard like screens to analyze what is going on with the services that you are calling to make business decisions?

3) 您的路线是否因业务决策而发生很大变化?例如，因为贵公司正在根据合作伙伴关系或成本更改提供商而调用不同的 Web 服务?

3) Are your routes changing a lot based on business decisions? Like for example calling different web services because your company is changing providers based on partnerships or costs?

4) 5 年内您的系统交互(和骆驼路线)会有多大?

4) How big is going to be your systems interactions (and camel routes) in 5 years?

5) 您是否需要遵守标准或法律规定?

5) Do you need to fulfil a standard or legal regulations?

如果最后 5 个问题的答案是否定的，那么使用骆驼并将 Web 服务编排保持在骆驼路线中是可以的，因为这只是保持代码清洁和可维护的一种方式，但它会始终隐藏在你公司的其余部分.

If the answers for the last 5 questions are no, using camel and keeping the web services orchestration in a camel route is fine, because it's just a way to keep your code clean and maintainable, but it will be always hidden from the rest of your company.

这篇关于Camel 与 BPM 中的工作流程的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！