In this review, we inaccurately stated that we ran the WaltzDB benchmark on ILOG JRules 6 and Fair Isaac Blaze Advisor 6.1. Although we were able to run the benchmark on Blaze Advisor, we were not able to do so on JRules. As noted in the review's supplementary performance chart online, we thus reported one of two benchmark results provided by ILOG. We believed this number accurately reflected JRules' performance. Since that time, ILOG has asserted that the performance number we reported was based on a first-generation RETE algorithm and not the current algorithm which the product now uses. We plan to perform further testing of our own to better assess the performance capabilities of ILOG JRules and will provide those results when they are available.
We’re all familiar with the conventional relationship between the business department and IT: The business department needs a new application or they need to change an existing application. They approach IT and ask how long it will take and how much it will cost. If within budget, IT gathers what it calls requirements and, after approval of the requirements, begins coding. Then comes the testing, changes, finger-pointing, backroom dealing, and more finger-pointing. In technical terms, IT has responsibility for both the validation of the application (Did we build the right system?) and the verification requirements (Did we build it properly?).
A BRMS (business rule management system) isolates the pure business logic of a project from the control logic and presentation code, and puts it into a rule base space. Effectively, a BRMS moves verification back to the business department where it belongs. Using a BRMS, the business user, not the IT department, writes the rules, change the rules, and delete the rules. The IT department is responsible for the construction of the system so that it is fast, scalable, and easily maintainable.
Fair Isaac’s Blaze Advisor and ILOG’s JRules are the longtime leaders in enterprise BRMS. JRules has always played catch-up to Blaze Advisor on rule building and management, but has led Blaze in speed. Now, as each reach version 6, JRules has some advantages in rule management and Blaze Advisor has turned on the after-burners, surpassing JRules in performance. I have finally compared these two solutions head-to-head, ringing all the bells and blowing all the whistles. I also ran the Waltz DB benchmarks on both rule engines for speed comparisons.
In interpreting benchmark results, remember one thing: They are general in nature and stress the engine in ways that your company may or may not need to, especially if the rules in your application are not especially interactive. (Read a more in-depth discussion of the classic rule benchmarks, or read a broader look at BRMS.)
What does a BRMS do for the bottom line? Last November at the annual Business Rules Forum I heard customer after customer regale audiences with how they had saved incredible amounts of time and money by using a BRMS. How much? Some reduced the time required to make changes from months to days or hours or minutes. Some now make changes within minutes, test within an hour or two, and put them into production the same day.
Fair Isaac Blaze Advisor 6.1
Blaze Advisor 6.0 and 6.1 are virtually the same except for one thing: speed. Unlike previous versions, Blaze Advisor 6.1 uses the Rete III algorithm that Fair Isaac obtained when it purchased RulesPower Technology last year. The speed increase, compared to previous incarnations of Blaze Advisor, is phenomenal. For example, Blaze 6.1 completed the Waltz DB 16 benchmark on my Windows XP machine (2.2GHz and 1MB of RAM) in 3.5 seconds, putting Blaze far ahead of JRules (88 seconds) but still a few steps behind OPSJ from Production Systems Technologies (1.6 seconds), still the fastest thing on the planet Earth. Take a gander at my benchmark results.
Blaze Advisor uses a form of backward chaining that uses a “when needed” flag on a rule as well as a “when changed” flag on attributes, helping to speed the processing of certain common problems such as configurations and resource management. In addition, Fair Isaac has built in score models for insurance applications, loan applications, and other financial problems. The rules can use either developer-centric dot notation or they can use regular English (or French or whatever language). As in JRules, however, these regular expressions must be added by the programmer during the development process. Blaze Advisor has always been one of the most friendly of the BRMS tools to business users, providing pleasant graphical development environments and understandable rule flow charts, decision tables, rule trees, and object models.
Reporting remains one of the best things about Blaze Advisor. Built-in reports will tell you anything about any object, rule, agenda stack, rule node, or anything else. You can report cross references between rules and objects, making it easy to see which objects are used by the rules, which rules use a specific object, and so on. Because Blaze Advisor uses standard tags, you can document author, version, exceptions, and virtually anything else you want to keep track of.
Blaze Advisor remains one of the better rule-management systems for the enterprise, combining a full-featured rule repository, business-friendly rule building, and reporting on almost anything that can be thought of by either the business user or the developer. Version 6.1, thanks to the incorporation of Rete III, now moves Blaze into the front of the pack in performance. GUI and language implementation could be better, considering the asking price. Fair Isaac should also make Blaze Advisor’s developer tools available as Eclipse plug-ins.
ILOG JRules 6.0
JRules 6.0 brings to the table a lot more “goodies” than earlier versions. For one, the BR Studio (formerly a downloadable freebie) is now part of the suite and works with Eclipse 3.0, IBM Rational Application Developer, and IBM Rational Software Architect. The Rule Team Server now allows rule administrators to assign various levels of responsibility, and control access to the rules themselves, based on user roles. The JRules Repository has been divided into two sets of rule repositories (one for business users and one for developers) that are kept in synchronization by the Rule Execution Server.
Permission levels are granular to such an extent that they can support multiple projects across large groups of developers and business users. You can set permissions for each individual by 11 different roles (such as modeler, programmer, knowledge engineer, or business analyst), with the permissions associated with each role being further subdivided into five or seven more levels.
The other really cool rule management feature is the separate repositories for the business analysts and developers. The developer repository is basically a “checked-out” version of the business analyst one. The two sides can be synchronized at any given time, but there is a date/time problem: By default JRules teams located in different time zones will see the rules execute in the time zone where the rules are located rather than the time zone of the user. An update, version 6.0.1, adds a feature that allows the use of either time zone.
On the down side, ILOG made a number of changes that make the tool far less easier to use for both the experienced programmer and the experienced AI geek. No longer are PDF manuals included in the release (they are online but require an ILOG id and password), and the formerly user-friendly documentation has taken a sharp turn for the worse. Finding the information you need can be nightmarishly difficult. Considering that version 6.0 is by far the most complex and difficult-to-understand implementation that ILOG has ever delivered, now was not the time to hobble the documentation.
Further, JRules no longer provides a way for developers and engineers to access the rules and the standard ILOG Rule Language “irl” files in the same tool. Developers can generate and access “irl” files when using the Eclipse-based BR Studio, but the rules are accessible only through the JRules GUI -- a fine tool for business users but painful for geeks. Developers and engineers need a way to work with the rules and the “irl” files in the same place.
Blaze Advisor and JRules continue to lead the BRMS pack in features suitable for enterprises, and both should be on the consideration list for most enterprise deployments. If you need great reporting templates, maximum speed, and lots and lots of factory support, Blaze Advisor is probably the answer. If rule building and rule management are more important than runtime performance -- if you need different views of the rules for different classes of users, or you want to customize the rule-building GUI and language for your business or industry -- then JRules may be the better choice. The pricing of the JRules starter pack, which includes unlimited use of BR Studio across the company, is also quite favorable.
Rule Management (30.0%)
Developer tools (20.0%)
Overall Score (100%)
|Fair Isaac Blaze Advisor 6.1||10.0||8.0||9.0||8.0||9.0||10.0|
|ILOG JRules 6.0||7.0||9.0||7.0||9.0||8.0||8.0|
Having trouble installing and setting up Win10? You aren’t alone. Here are many of the most common...
It's all about knowing how to build an open source community -- plus experience running applications in...
Win7 Update scans got you fuming? Here’s how to make the most of Microsoft’s 'magic' speed-up patch
Sponsored by Puppet
Sponsored by Intel
Look to these clever open source tools to keep secrets out of source code, identify malicious files,...
From a simple platform for beginners to an expert-level development workbench, there's an IDE for most...
Technology may appear to be smart, but in most cases it merely has great logic. That’s not the same as...
Stop obsessing about the latest overhyped security threats. Delve into your own data about successful...