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.
FICO Blaze Advisor is suitable for cases where you have to deal with rules and where you want to customise the rules based on the business need then this product is very good to use. Also it provide easy deployment so, wherever there is frequent changes in deployment then this tool is good to use since it provides the direct deployment.
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.
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.
Overall using FICO Blaze Advisor is good experience since change in any existing things were very easy in FICO Blaze Advisor, and I was easily able to make the change and deploy the things directly so that was real quick to check the things in the production, and this is the best point about FICO Blaze Advisor.
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.
