For anyone who doesn't know, Apache Camel is an open source integration framework based on unified resource identifiers (URIs), enterprise integration patterns, and Bean integration. During JavaOne, Rob Davies, CTO of FuseSource and Apache Camel committer, explained his current project, which correlates events for simple implementations of complex event processing (CEP).
During a video interview at JavaOne 2011, Davies talked a bit about what's new for the Apache Camel project. The Apache community is now deciding what's going into Camel 3, which may be out as soon as next year. It's a collaborative process and there is talk about really streamlining the API to match the new ways that people are using Apache Camel.
Davies is surprised by the current uptick in popularity of Apache Camel. Davies claims that the highly active community around Camel has provided well over 100 components that integrate Camel with other systems. Davies says that he's talked to multiple attendees at the conference who are using Apache Camel to integrate their legacy systems and wrap services around them.
According to Davies, Apache Camel can be as light as a couple of JARs that can be deployed in WebLogic, Tomcat, Service mix or of course Aoache Karaf, and could also be embedded into a messaging bus like ActiveMQ. "Because it's so flexible," Davies says, "[it is being used] as the duct tape to make things work and hold things together."