在骆驼的工作​​流程BPM VS [英] Work Flow in Camel vs BPM

问题描述

我们已经使用的Apache骆驼作为工作流engine.First Wehave WebService的一个，并等待响应并基于响应呼叫的WebService 2或WebService 3.Its纯的工作流程和具有耦合工作流程步骤像this.I的已经得到机会少到一个BPM产品的工作，如JBoss BPM等除了长时间运行和人工任务的支持，我们必须选择一个BPM产品的任何其他正当理由吗？如果我们的项目不是都需要长时间运行和人工任务的支持，我们可以使用骆驼或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 ?

谢谢，
狮子座。

Thanks, Leo.

推荐答案

是啊..作为安托万提，从技术角度来看，这可能听起来很类似，但是如果你使用骆驼作为一个状态机来移动数据你没有做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服务编排在骆驼的路线是好的，因为它只是一个让您的code清洁维护的方式，但它会永远从公司的其余部分隐藏起来。

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.

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