Let's talk about exceptions ...
How do you handle exceptions? Do you think upfront about the type of exceptions that you want to catch or do you just let the outside world handle it?

-- Jeroen van Bergen in JW Blogs

Newsletter sign-up

Sign up for our technology specific newsletters.

Enterprise Java
View all newsletters
Email Address:
JavaWorld.com

Clash of the Java rule titans

Blaze Advisor vs. JRules

By James Owen, InfoWorld, 07/17/06

July 17, 2006— 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, changes the rules, and deletes 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. 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.2 GHz 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 (http://www.infoworld.com/4286).


For more enterprise computing news, visit InfoWorld. Story copyright InfoWorld Media Group, Inc.

Discuss

Start a new discussion or jump into one of the threads below:

Subject Replies Last post
. Clash of the Java rule titans
By JavaWorld 		2 11/03/06 06:31 AM
by Anonymous


Resources