This is private and confidential post. The information is not, and has not been, reasonably obtainable without the consent by other persons by use of legitimate other than discovery based on a showing of special need in a judicial or quasi-judicial proceeding.

Except Google and U.S. government ... ...

Sorry T, I've been meaning to respond to this for a while now. Regrettably I do not have any Camel experience to be objective in a Camel versus SI call. Like Camel, SI provides an abstraction of the standard Enterprise Integration Patterns.

+James Gemmell I'm reading SI vs. Camel article now. Someone says it's because of fluent API, but will dig out more.

Camel like takes the momentum right now.

Having now easily converted a simple SI app to Camel en route to Akka, I'm most impressed by the DSL. Especially the ability to integrate the XML DSL directly into the Spring app context.

+James Gemmell J, now I'm more leaning to Spring Integration over Apache Camel now, after more than 12 months work using Camel.

Found an interesting link on Stake Overflow:

1) The effect that Spring Boot has had on developer productivity for Spring Integration

2) The effect of Spring XD has had on making Spring Integration applications available with no code compilation - also Spring XD sources and sinks are simply Spring Integration channel adapters, when you're looking to extend Spring XD.

3) The effect of Spring XD has had on making unifying Spring Integration, Spring Batch, Spring Data in one stack, effectively bringing batch and stream processing, HDFS/Apache Hadoop support, and much more to Spring Integration.

4) The effect of Spring Integration 4.0 Java DSL