7 Reviews and Ratings
10 Reviews and Ratings
No answers on this topic
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
It fits perfectly for SOA and EAI architecture with large numbers of services that required to be wired to each other, the binding virtualization is quite good to simply this part. For the simple scenario of orchestration and /or ESB architecture could be a better use traditional stack.Incentivized
Writing rules with business focusRules evolution and maintenanceseparate business logic from program codeIncentivized
reduce the number of http port required by servicessimplified the binding connection amongst serviceshigh scalability and fast deployment of applicationsIncentivized
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
health check of services and application features has been released with a lot of bugs that have never been fixedit is not so simple to apply the security policy to service/reference bindingIncentivized
I did not participate in drools choice. I can only compare drools with the previous situation which was using nothing.Incentivized
TIBCO service grid has been chosen as a natural selection of the TIBCO product evolution. The high flexibility and the binding virtualization fits very well with client needs for its EAI applications due to the huge number of services and applications, the management of application dependencies during deployment, the advantage of perfect integration with EMS for loggingIncentivized
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
The integration of old BW with BWSE and its interface quite similar to design time has reduced the cost of training for developersThe TIBCO support for this product is no the best and clients complains too much about this. This required to find a workaround or force the client to move to new/or different product. Huge impact on ROIIncentivized