Drools vs. Progress Corticon Business Rules Engine

Drools is well suited for big projects where business logic and rules must be separated from program code. So they can evolve when business evolves without being tied to code evolution and deployment.

Incentivized

Suited for any place where complex business rules need to be separated for ease of flexibility.

• Writing rules with business focus
• Rules evolution and maintenance
• separate business logic from program code

Incentivized

• Handle complex business rules.
• Test different scenarios after changes have been made.
• Allow for version control and auditing of queries and responses.

• Fusion doesn't support persistence of working memory, which brings some extra high availability risk to our business.
• Guvnor still has a lot room to be implemented, it is not so user-friendly for non-technical people, so a lot of business users complain it is hard to master.
• Rule execution server doesn't even have JMX implemented, hard to be monitored.
• Drools is still lacking support for key Web services standards.

Incentivized

• The UI could be made more appealing.

OpenRules provides the non-technical Excel way for a business user to easily modify and manage the rules. Sometimes we found Drools is a little bit overkill for some small and quick projects and we found Roolie is a not bad option as Drools alternative.

Incentivized

Corticon is way easier and allows for testing.

• The IT department quickly adopted Drools as it is a very good java-based rule engine, which saves a lot of time to meet the project timeline and balanced our business requirements.
• Recently we start considering the OpenRules, which may be more business user-friendly.

Incentivized

• It has definitely had a positive ROI. Instead of having developers try to figure out these complex rules and how to code them in a flexible way, we now have business analysts using Corticon.