|
|
Fri Jan 09 16:26:38 GMT 2009 Rule Engine* It does seem that it's important to limit the number of rules, indeed any system with enough rules to need sophisticated algorithms to get good performance probably has too many rules to be understood. * Similarly I'm inclined to think one should be wary of rules that do a lot of chaining. * As in many places, testing is often undervalued here, but implicit behavior makes testing more important - and it needs to be done with production data. * While building a rules system, I'd look to do things that would cause EarlyPain with modifications of the rule base. http://martinfowler.com/bliki/RulesEngine.html (google search) (amazon search) second |