<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
Has anybody tried to evaluate the different rules engines in the
interests of using it in their companies' technology stack? I've got
to do some due diligence, so need to evaluate the others.<br>
<br>
Specifically, we're looking at a dynamic data model (not OO), and so
that needs to be supported in some way (which I am heavily evaluating
for drools :)). There are plenty of other criteria, but the show
stoppers are:<br>
<ul>
<li>unable to support a dynamic data model (being able to type
different structures with the same object base, and to a lesser degree
being able to compose those types into other dynamic types)<br>
</li>
<li>Lack of support (either community or commercial)</li>
<li>Lack of rule management (activation and expiry dates for rules)</li>
</ul>
Also high on the list are:<br>
<ul>
<li>DSL support</li>
<li>rule composition and reuse (I don't really know much about how
this this concept plays out with rules yet)</li>
<li>Testing: the person creating the rules can write the tests, in
the same designer<br>
</li>
<li>Auditing and understanding how the engine got to the state it's in</li>
</ul>
So far I've found about 15-20 engines. Hopefully most of them will
fall out of the early criteria :)<br>
<br>
Cheers<br>
<br>
Stephen<br>
</body>
</html>