当使用Spring的集成与骆驼？ [英] When to use Spring Integration vs. Camel?

问题描述

当我假设Spring集成将最有意义的最近的一个项目需要一些（JMS）消息能力的有经验的Spring用户（<一href=\"http://stackoverflow.com/questions/3012802/how-to-leverage-spring-integration-in-a-real-world-jms-distributed-architecture\">more详细信息）。几天以后，与Spring集成工作仍感觉就像给了你必须配置带来了一些请求 - 响应（监听不同的JMS队列）代替通信信道的数量很多的配置开销。

As a seasoned Spring user I was assuming that Spring Integration would make the most sense in a recent project requiring some (JMS) messaging capabilities (more details). After some days working with Spring Integration it still feels like a lot of configuration overhead given the amount of channels you have to configure to bring some request-response (listening on different JMS queues) communications in place.

所以我一直在寻找一些背景资料骆驼是如何从Spring集成不同，但它似乎像信息从有pretty备用，我发现：

Therefore I was looking for some background information how Camel is different from Spring Integration, but it seems like information out there are pretty spare, I found:

• http://java.dzone.com/articles/spring-integration-and-apache
（在Spring集成与骆驼实现现实世界的集成方案，从2009年12月之间非常中性的比较）

• http://hillert.blogspot.com/2009/10/apache-camel-alternatives.html （与其它解决方案相比骆驼，2009年10月）


• http://raibledesigns.com/rd/entry/taking_apache_camel_for_a （太Raible，2008年10月）

• http://java.dzone.com/articles/spring-integration-and-apache (Very neutral comparison between implementing a real-world integration scenario in Spring Integration vs. Camel, from December 2009)
• http://hillert.blogspot.com/2009/10/apache-camel-alternatives.html (Comparing Camel with other solutions, October 2009)
• http://raibledesigns.com/rd/entry/taking_apache_camel_for_a (Matt Raible, October 2008)

问题是：您使用比其他的一个堆栈有什么经验？在这种情况下，您会推荐骆驼是Spring集成缺乏支持？你在哪里看到的每一个优点和缺点？来自真实世界的项目任何建议是高度AP preciated。

Question is: what experiences did you make on using the one stack over the other? In which scenarios would you recommend Camel were Spring Integration lacks support? Where do you see pros and cons of each? Any advise from real-world projects are highly appreciated.

推荐答案

我们选择骆驼比弹簧集成，因为一口流利的API是非常好的。实际上，我们在Spring项目中使用它，并使用Spring配置的一部分。编程API的清晰，有一大套明智的组件。

We choose Camel over Spring-Integration because the fluent API is really nice. We actually use it in Spring projects and use Spring to configure part of it. The programming API's are clear and there is a large set of sensible components.

我们做了一个小规模的枪战，基本在那个时候对我们的要求骆驼赢了。我们用它主要是为了内部的数据文件传输到/从外部各方通常需要格式转换利用它发送FTP / SFTP / ...或将其附加到电子邮件并发送出去。

We did a small scale shootout and basically at that time for our requirement Camel won. We use it mainly to transfer internal datafiles to/from external parties which usually requires format conversions sending it using ftp/sftp/... or attaching it to an email and sending it out.

我们发现，编辑 - 编译 - 调试周期缩短。使用Groovy尝试​​建立路由添加的奖金。

We found the edit-compile-debug cycle reduced. Using groovy to experiment setting up routes are added bonuses.

Spring的集成是一个伟大的产品过了，我肯定会满足我们的需求了。

Spring-Integration is a great product too, and I am quite sure it would satisfy our needs too.

这篇关于当使用Spring的集成与骆驼？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！