Since we're on a major migration process of this website, some component documents here are out of sync right now. In the meantime you may want to look at the early version of the new website
https://camel.apache.org/staging/
We would very much like to receive any feedback on the new site, please join the discussion on the Camel user mailing list.

Camel CEP

Complex Event Processing or Event Stream Processing are approaches of processing streams of events, usually from multiple sources.

One approach to CEP with Camel is to use the Esper endpoint then use Esper's SQL-like DSL for working with event streams.

Another approach to CEP with Camel is to use Camel RX which provides a typesafe DSL in Java, Scala, Groovy, clojure for processing events in a natural collection-like way (while being high performance and asynchronous under the covers). Camel RX uses the RxJava API which is a JVM port of the Reactive Extensions

CEP with Camel RX

Camel RX provides various ways to get an Observable<T> which provides the typesafe DSL for processing events on a single stream.

Once you have an Observable<T> you can then:

Note that at the time of writing, some of the RX APIs have not yet been ported to RxJava so that some of the core CEP functions are not yet implemented. e.g. these functions will really complete RxJava's CEP coverage:

So until RxJava hits 0.7 milestone there is limited support for combining streams; but that should hopefully be fixed soon. I'm sure the RxJava folks would welcome contributions on those issues (smile)

© 2004-2015 The Apache Software Foundation.
Apache Camel, Camel, Apache, the Apache feather logo, and the Apache Camel project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.
Graphic Design By Hiram