Unfortunately CEP isn’t really a focus of the project. Having said that, it is possible. For example, the old documentation for sliding windows still worked the last time I checked:
https://apacheignite.readme.io/v1.4/docs/sliding-windows <https://apacheignite.readme.io/v1.4/docs/sliding-windows> And, of course, you can using things like Continuous Queries to listen to changes in caches. The difference between Ignite and Spark. Flink, etc. is mostly down to programming model and storage. Neither Spark nor Flink have any persistence but Ignite does (both in memory and on disk). All three have different programming models; which is best depends on your use case. Many people choose Ignite as it does “everything.” Others pick a combination, taking advantage of the specialisation in some tools at the expense of more integration work. Regards, Stephen > On 17 Sep 2019, at 09:24, Ignite Enthusiast <ignite_en...@yahoo.com> wrote: > > Anyone ?? > > On Wednesday, September 11, 2019, 3:29:32 PM GMT+5:30, Ignite Enthusiast > <ignite_en...@yahoo.com> wrote: > > > I am trying to build a CEP where a Complex event needs to be generated on a > set of input events (3 Chassis hot events) over a specified time window (10 > seconds, for eg) and I am trying to evaluate Apache Ignite for this. > > Are there any examples of how to do Complex Event Processing using Ignite? > The following wiki page hardly seems to help. > > https://apacheignite.readme.io/docs/streaming--cep > <https://apacheignite.readme.io/docs/streaming--cep> > > > Also, how does Ignite CEP implementation compare with others ? (like Apache > Spark, Apache Flink, etc)
