Tuesday, June 15, 2004

XML rule engine - QuickRules

Another Java based XML rule engine - QuickRules, I was not aware of. They also have a DecisionTable editor. The .NET integration goes through COM, so that is just a marketing line. There is also some workflow editing provided. But not on the level as the BizTalk 2004 orchestration. Anyway have a closer look at this product if Java (J2EE) is your target application server.


Kyung-Mo Jung said...

I downloaded it and evaluate. It looks some smart, but it seems not business oriented but some IT oriented. Business users can handle rules via Web, however it looks difficult for business users to create or modify rules at first time.

Rajgo said...

QuickRules(The Java Version)is a BRMS for the Java & the J2EE platforms. It is not targeted at the .NET platform.

QuickRules.NET is YASU's BRMS for the .NET platform. It is a pure C# implementation, and integration is not through COM.

There seems to this confusion generally about Workflows and Rule flows. What the QuickRules products provide is called a Flow Ruleset. Essentially, you can define the sequence of execution of your rules in a graphical format. This is in contrast to Rete Rulesets where the Rete algorithm determines the sequence of the ruleset at runtime.
Other vendors like Blaze Advisor also offer Graphical Sequential Rules

I have written a post about the Workflow Foundation and Business Rules Systems in 2 posts here,
2. WWF & BRMS - Integration Scenarios

Marco Ensing said...


Thanks for the clarification on the QuickRules.NET. I'm sure you have this from a trusted source.

I don't know if there is any confusion between the difference of rule engine or workflow engine. But it can never hurt to clarify this further.

Interestingly enough the new Rule Engine from Microsoft is NOT going to use a Rete engine. You can read more about this here. A Rete inference engine is not the only way to execute declarative defined rules.


Rajgo said...

Hi Marco,
I am the Product Manager for QuickRules.NET, so I am pretty sure about the source :) .

Regarding Rule Engines, you are bang on the Dot. Rete is not the only rule engine algorithm.

The Rule Engine in WWF is a forward chaining engine that does not use Rete.
There are other types of rule engines possible.

In QuickRules, Decision Tables, are evaluated using a simpler, faster Top->Bottom, Left->Right Engine that is not Rete

Sequential Rule Flows are executed using a simpler Rule engine that is not Rete.In case of sequential rules, there is no inference involved

There is research going on on Ripple Down Rules these days, but I am not very knowledgeable on that subject

make files explained if you did not grew up with them

Here is a nice post on how to define makefiles for a go project and actually teaching you some makefile constructs: https://sahilm.com/mak...