The document introduces Drools, an open source rule engine platform. It discusses some problems with implementing rules in Java and how Drools addresses these issues. It provides examples of rules in Drools and how the RETE algorithm works behind the scenes. The document also outlines when not to use Drools and lists some alternative rule engine options.
8. Problems in implementing with Java Frequent changes to rules(conditions) Lack of centralization of rules Difficult to analyse and manage Non technical people(Business Analysts ..) can't create/update rules Performance
9. Introducing Drools Basically, a rule engine Rule Engine: Platform that provides functionality to manage rules Rule: An if else condition (Business Logic)
17. When not to use Drools If your business logic is well defined/static and doesn't change often, you don't need to change rules at run-time. If your rules are simple, self-contained, and usually spanning only a single object (for example, a check that user's age is less than 21). If you have a memory constrained environment. If your project is a one-shot effort and it will never be used again or maintained over time.
18. Alternatives to Drools ILOG (now IBM)JRules Fair IsaacBlaze Advisor Corticon's BRMS, Haley (now Oracle) Business Rules Engine PegasystemsPegaRules, Production Systems TechnologiesOPSJ CLIPS OpenRules or Jess