The Fastpath execution mode provides augmented sequential compilation and execution of a rule project. Like the ILOG JRules sequential mode, Fastpath is a sequential mode of execution. However, it also detects semantic relations between rule tests during the pattern matching process, like RetePlus.

Look at this illustration of Fastpath operation:

In Fastpath, the rule engine can use a working memory referencing application objects, or ruleset parameters. Fastpath performs the pattern matching process, as in RetePlus, by creating a tree based on semantic relations between rule condition tests (step 1).

For each match, a rule instance is created and immediately fired. When a rule instance is fired, it may modify objects in working memory, but these modifications are not taken into account and the rule engine does not repeat the pattern matching process (step 2). The action of the fired rule may also set an output ruleset parameter.

Fastpath combines features of RetePlus for pattern matching and features of sequential for rule firing. In this sense, it compares well for correlation types of applications as well as for validation and compliance applications.

Like the sequential execution mode, the Fastpath execution mode is a stateless mode that is dedicated to matching objects against a very large number of rules that individually perform simple discriminations or light join tests. Such a set of rules is best fired in sequence directly without any agenda support. In addition to its advantages as a variant of the sequential mode, the Fastpath execution mode is designed to further optimize the execution of the compliance and validation rules, which constitute a substantial part of business rules.

Related Concepts

Related Tasks

Related Samples and Tutorials