Camel vs Spring Integration

Hi!
I have been interested in taking a closer look at Camel and/or Spring Integration for some time.
Are they to be considered as competing or complementary products?
If they are competing, then:
Since you are Camel-guys, I won't ask you for the reason to choose Camel, but rather for the reasons to choose Spring Integration over Camel. :-)

I realize that you probably spend a lot of time with Camel and not as much, if any, with Spring Integration, so please disregard my questions if you lack experience of the latter.
Thanks in advance!

Disclaimer: yeah, I'm a Camel guy

Both frameworks are definitely related. They both try and fill the space for a lightweight integration framework that is deployed into something else, like an ESB. They are both not ESBs.

Its hard for me to argue for Spring Integration since I use Camel so much

but I have heard from others that a big win for Camel is the number of supported transports and APIs that Camel can talk to. Spring Integration has a much smaller set of connectivity options last time I checked. Also personally, I find Camel DSLs much cleaner and are generally easier to read.

Actually, Camel does provide a Spring Integration component http://camel.apache.org/springintegration.html so you can produce and consume from SI endpoints in Camel if you'd like to use both.

Hope this helps!

Cheers,
Jon

Hi!

Jonathan Anstey wrote:
Hope this helps!

Indeed!
Now that I know that Spring Integration and Camel can be integrated, I just have to look at them both!
Thanks again!

A reason to pick SI over Camel would be the Spring name.
Personally I doubt the framework would have had a chance if it was not created by Spring.

I just wrote a blog post with my experiences using Apache Camel and Spring Integration (and Mule ESB):

Spoilt for Choice: Which Integration Framework to use – Spring Integration, Mule ESB or Apache Camel?

Hi!
@Kai: Thanks a lot for posting the link and for the article. Indeed interesting reading!
Best wishes!