Win a copy of Head First Android this week in the Android forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Liutauras Vilda
Sheriffs:
  • Jeanne Boyarsky
  • Rob Spoor
  • Bear Bibeault
Saloon Keepers:
  • Jesse Silverman
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • Al Hobbs
  • salvin francis

Camel vs Spring Integration

 
Ranch Hand
Posts: 2198
1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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!
 
author
Posts: 9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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
 
Ivan Krizsan
Ranch Hand
Posts: 2198
1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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!
 
author
Posts: 18
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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.
 
Ranch Hand
Posts: 76
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
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?
 
Ivan Krizsan
Ranch Hand
Posts: 2198
1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi!
@Kai: Thanks a lot for posting the link and for the article. Indeed interesting reading!
Best wishes!
 
reply
    Bookmark Topic Watch Topic
  • New Topic