[jboss-jira] [JBoss JIRA] (DROOLS-1221) Add fail-safe and scalability functionality to the Drools (CEP) rules engine

[Youcef HILEM (JIRA)]

    [ https://issues.jboss.org/browse/DROOLS-1221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286314#comment-13286314 ] 

Youcef HILEM commented on DROOLS-1221:
--------------------------------------

Hi Tom Pijl ,
The second solution (http://redhat-italy.github.io/hacep/) is a Scalable and Highly Available architecture for Drools Complex Event Processing. HACEP combines Infinispan, Camel, ActiveMQ and obviously Drools in a unique way to obtain:
- CEP Automatic horizontal scalability
- CEP Automatic fail over

An hi-level technical overview of HACEP can be found here : http://redhat.slides.com/ulandini/hacep-1

About my environment, I will adapt this solution by integrating Drools with Kafka, Kafka Streams and Apache Geode. The domain is parcel track and trace (http://www.informit.com/articles/article.aspx?p=2140992&seqNum=5).

> Add fail-safe and scalability functionality to the Drools (CEP) rules engine
> ----------------------------------------------------------------------------
>
>                 Key: DROOLS-1221
>                 URL: https://issues.jboss.org/browse/DROOLS-1221
>             Project: Drools
>          Issue Type: Feature Request
>          Components: core engine
>    Affects Versions: 6.4.0.Final
>         Environment: Drools (CEP) Rule engine 6.4.0.Final
>            Reporter: Tom Pijl
>            Assignee: Mario Fusco
>
> The Drools Rule engine is currently not fail-safe and scalable which is a requirement for Cloud deployment.
> Add a possibility to persist the state of the working memory after each state change (perhaps linked to the fireAllRules()?) and related to that the possibility to restore the state  in case of a crash (fail-safe requirement).
> This persistent state store can also be used to synchronize multiple engine instances (scalability requirement).
> Of course this has major impact on the performance of the engine, but it is the only way to make the engine useful in a multi-tenant Cloud environment



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)