Drools vs. SMARTS Decision Management Platform

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

Smarts is well-suited to handle rules orchestration for complex decision flows where there's a need for advanced functionality and reusable components or assets. It is very useful for scenario testing, modeling, and dashboarding. These capabilities give you robust insights and help you optimize your decisions. It is less appropriate for very simple decisioning needs.

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

Incentivized

• 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

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

• 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