Montag, 11. August 2014

Research and Development...

one more time we took a look at some really impressive CEP solutions and thought about their design influences on RapidECA. But we haven't enough resources to do research and development at the same time. So one consequence is that we didn't work constantly on the code base of RapidECA during the last couple of weeks.

But one really important aspect why we develop RapidECA is fun - to reseach for sophisticated approaches/technologies brings us a lot of fun!

During our research we took a closer look at the etalis project.
etalis is completely written in Prolog and highly optimized for CEP scenarios. It's very easy to use from Java/Groovy by using tuProlog. etalis is fast, expressive, and elegant.

Check it out:

Stay tuned and follow us on g+ or twitter!


RapidECA Team

Montag, 7. Juli 2014

Upgrade of RapidECA Node & Plugins...

in June we've upgraded RapidECA Node and all plugins for working with Grails 'v2.3.11'. As well we've changed the version of Drools in the 'rapideca-drools-plugin' from '5.5.0.Final' to '5.6.0.Final'.

The next thing was that we ran into problems with GroovyServ when we worked on RapidECA Glue. Take a look here for more details:
Yasuharu Nakano (project lead of GroovyServ) is working on a new release where this issue will be fixed.

The next couple of weeks we're going to upgrade RapidECA Glance for working with Grails 'v2.3.11' and beyond that we're going to implement the new REST features of Grails.

That was the news - stay tuned and follow us on g+ or twitter!


RapidECA Team

Montag, 2. Juni 2014

Event Correlation & Analysis as a Microservice ...

that's the fundamental concept behind RapidECA. When you take a look at the vision slides you can see that all components of RapidECA are loosely coupled via REST. So the RapidECA ecosystem can be integrated very easily in your environment and extended by your own RESTful 'Microservices'.

At the beginning of 2013 when we made our first steps with RapidECA, 'Microservices'
weren't a hype. But at this time RESTful APIs were already a de facto standard for building interoperable services. Today we see a lot of new 'Micro-Frameworks' in the Java world like Vert.x, Spring Boot, Spark, Ratpack, etc... that reinforce the trend of designing "Microservice Architectures".

Right now, we're very happy to see that the design decision to create RapidECA as so called 'Microservice' seems to be the right one. An interesting post about 'Microservices' can be found here:

During the last month we've worked on the Rule Management capability which will be a part of the Event Management Pack feature in the future. The following figures shows some more details:

The RuleEngine is able to load different RuleBases. A RuleBase consists of several containers like RulePacks and RuleSets that help you to organize your Rules. All RuleBase components are cloneable, so that new Rules can be created without effort.

That was the news - stay tuned and follow us on g+ or twitter!


RapidECA Team