It supports a wide range of components and messaging patterns, is lightweight and has a flexible deployment model (standalone, spring, maven, webapp, OSGi, etc).
eh, we did a productivity test on coding pure java vs. ESB (mule and spring integration). We had 3 developers do the same thing in all 3 versions (mule, SI, and just pure java with no ESB). They finsihed 6 times faster when not using an ESB and we gave alot of things in the problem that would leverage the ESB, but in the end it did not help....all the xml coding and confusion of the api usages led to really unproductive development teams. Not only that, it is hard to find ESB developers on the market as well.
NOTE: We even took an advanced spring integration guy that had been doing it and he also was faster in pure java to complete the code. He loved spring integration and after taking my test, he changed his mind.
ie. be warned of the huge productivity loss that using the wrong framework can cause. 6 times is a huge penalty. I mean 1 month vs. 6 months is a big difference.
A 6 times productivity loss is worth taking one week out and doing your own developer productivity test. Some argued with me that they didn't know the framework yet which is why we got an advanced spring integration guy to take the test.
Also, make sure your test takes at least an hour or so....just develop some fake but realistic requirements from the application that you are going to write anyways so you make progress on your application while running the study. I would be interested to see more results posted as well.
As per your requirement, I would suggest you to go with WSO2 ESB. Its and 100% free and open source ESB (Apache License 2) and unlike other ESBs, with wso2 you don't have the commercial and community versions. So, what you download for free from WSO2, comprises of all the features that are available in 'commercial versions' of other ESB vendors. Also, WSO2 offers not just an ESB but a complete SOA Platform for your SOA needs.
For the requirement you mentioned above, there is a simple sample that you can try out.
发布评论
评论（4）
您也可以使用 Apache Camel 来实现此目的...
它支持多种 组件 和 消息模式，是轻量级并且具有灵活的部署模型（standalone、spring、maven、webapp、OSGi 等）。
you can also just use Apache Camel for this...
It supports a wide range of components and messaging patterns, is lightweight and has a flexible deployment model (standalone, spring, maven, webapp, OSGi, etc).
你已经回答了你自己的问题。是的，ESB 是一个不错的选择。您可以使用Mule。
第二个选项是异步消息传递，但它会很复杂，因为您必须正确编排服务。
You have answered your own. Yes ESB is good option. You can use Mule.
Second option is Asynchronous messaging but it will be complicated, because You have to orchestrate the services properly.
嗯，我们对纯 java 与 ESB（mule 和 spring 集成）进行了生产力测试。我们让 3 名开发人员在所有 3 个版本（mule、SI 和没有 ESB 的纯 java）中做同样的事情。当不使用 ESB 时，他们的完成速度提高了 6 倍，并且我们在问题中给出了很多可以利用 ESB 的东西，但最终它没有帮助......所有的 xml 编码和 API 用法的混乱导致了真正的问题。低生产力的开发团队。不仅如此，市场上也很难找到 ESB 开发人员。
注意：我们甚至聘请了一位高级 spring 集成人员，他一直在做这件事，他在纯 java 中也更快地完成了代码。他喜欢 Spring 集成，在参加我的测试后，他改变了主意。
IE。请注意，使用错误的框架可能会导致巨大的生产力损失。 6次是一个巨大的惩罚。我的意思是 1 个月和 6 个月是有很大区别的。
6 倍的生产力损失值得您花一周时间进行自己的开发人员生产力测试。有些人与我争辩说他们还不了解框架，这就是为什么我们找了一位高级 spring 集成人员来参加测试。
另外，请确保您的测试至少需要一个小时左右......只需从您要编写的应用程序中制定一些虚假但现实的要求，以便您在运行研究的同时在应用程序上取得进展。我也有兴趣看到发布更多结果。
eh, we did a productivity test on coding pure java vs. ESB (mule and spring integration). We had 3 developers do the same thing in all 3 versions (mule, SI, and just pure java with no ESB). They finsihed 6 times faster when not using an ESB and we gave alot of things in the problem that would leverage the ESB, but in the end it did not help....all the xml coding and confusion of the api usages led to really unproductive development teams. Not only that, it is hard to find ESB developers on the market as well.
NOTE: We even took an advanced spring integration guy that had been doing it and he also was faster in pure java to complete the code. He loved spring integration and after taking my test, he changed his mind.
ie. be warned of the huge productivity loss that using the wrong framework can cause. 6 times is a huge penalty. I mean 1 month vs. 6 months is a big difference.
A 6 times productivity loss is worth taking one week out and doing your own developer productivity test. Some argued with me that they didn't know the framework yet which is why we got an advanced spring integration guy to take the test.
Also, make sure your test takes at least an hour or so....just develop some fake but realistic requirements from the application that you are going to write anyways so you make progress on your application while running the study. I would be interested to see more results posted as well.
根据您的要求，我建议您使用 WSO2 ESB。它是 100% 免费和开源的 ESB（Apache 许可证 2），与其他 ESB 不同，使用 wso2，您没有商业和社区版本。因此，您从 WSO2 免费下载的内容包含“商业版本”中提供的所有功能其他 ESB 供应商的。此外，WSO2 不仅提供 ESB，还提供完整的 SOA 平台来满足您的 SOA 需求。
对于您上面提到的要求，有一个 简单您可以尝试的示例。
As per your requirement, I would suggest you to go with WSO2 ESB. Its and 100% free and open source ESB (Apache License 2) and unlike other ESBs, with wso2 you don't have the commercial and community versions. So, what you download for free from WSO2, comprises of all the features that are available in 'commercial versions' of other ESB vendors. Also, WSO2 offers not just an ESB but a complete SOA Platform for your SOA needs.
For the requirement you mentioned above, there is a simple sample that you can try out.