[
https://issues.jboss.org/browse/DROOLS-1221?page=com.atlassian.jira.plugi...
]
Tom Pijl commented on DROOLS-1221:
----------------------------------
Thanks [~youcefhilem] for these pointers.
The examples referenced in your first comment solves the high availability requirement at
the cost of Rules flexibility (insert, update and delete facts are not allowed), but it
didn't address the (horizontal) scalability requirement: distributing work over
multiple engines. A solution is mentioned in the slide set: implementing Event
partitioning, but the examples did notshow this.
I am still going through the project you referenced in your second comment....
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)