Drools vs. IBM Operational Decision Manager

As an open source rule engine and product suite, Drools is well suited for the small and middle scale business to manage and integrate the rules to build the rule-driven system which can process the business-critical data and events to produce the automated decision. It is better to use Drools in the well-secured environment (back-end behind the DMZ), not putting it on the customer-facing front or exposing it directly the to public where may bring direct security risk in the enterprise environment. Drools still needs a lot hardening on the security side.

Incentivized

IBM Operational Decision Manager can be used to manage complex business processes with less use of IT infrastructure and more use of centralized decision making. Decision-making depends on a logical framework and the creation of commands for better futuristic decisions with less time consumption and more precision and accuracy. IBM's Operational decision manager application is well suited for such scenarios where complex processes have to be streamlined.

Incentivized

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

Incentivized

• Excellent stability and performance, as well as the possibility to deploy more quickly.
• Simple but effective web-based user interface that enables us to make direct updates to our policies or rules.
• Effective rule Execution Server, which allows us to assess the rules and their performance
• After the rules are delivered, business users can make changes and keep them up to date without having to know a lot about technology.

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

• Business rule application development available only in Java, .net, and Cobol.
• Integration supports with legacy system need to be improved (Mainframe).
• Migration to latest -version (iLog JRules to ODM).

Incentivized

I did not participate in drools choice. I can only compare drools with the previous situation which was using nothing.

Incentivized

When compared to other vendors in the business rule management system, IBM Operational Decision Manager stands out in dimensions of rule engine capabilities, deployment flexibility, and ease of maintenance. It offers a wide spectrum of configuration options to build applications that can be used by developed by technical and non-technical/business users.

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

• It has a positive impact as it provides a great way to define business rules, execute them, update them, manage different versions of rules.
• Depending on the complexity of the applications, you can have thousands of rules.
• It provides a nice way to test the rules, run simulations with different scenarios, different scales of requests and verify the decisions, performance, etc., and that helps a lot.
• Since the decisions can be exposed through REST interface, it makes it very convenient to integrate with different applications, applications using different technologies.
• The Business console makes it easy for business users to be able to define, modify rules and not have to depend on IT to do a lot of that work. This helps in bringing the time to change and use the rules to be very short as well as lets IT do more IT related tasks and provide better value to the organization.

Incentivized