Going on 5 years ago, I wrote part 1. Now, finally, it’s time for the rest of the story.
Continue reading “Confessions of a production rule vendor (part 2)”
Recruiting: IBM Ilog vs. JBoss Drools
I received notice of a Victorian government position offering $106k, as follows, today:
BRMS Developer (WebSphere ILOG JRules)
You will have proven experience as a BRMS Developer within a Java/JEE environment using IBM‘s WebSphere ILOG JRules platform. You will have implementation experience using integration technologies (e.g. Web Services, JMS) and have the ability to liaise with and engage key stakeholders. Ideally you will also have knowledge and/or exposure to IBM‘s WebSphere integration suite (including the MQ Series).
This got a reaction out of me since we’re looking for people (although emphasizing logic, semantics, and English rather than any particular engine). At first, I thought it must be a Java job, but stakeholder engagement indicates this is a full-fledged knowledge engineering position.
$100k for anyone with strong, specific experience seems low. For someone that can understand objectives and translate requirements into operational business logic, it seems lower.
I’m surprised there isn’t more of an Ilog premium, too. JBoss Drools consultants can make more than this.
Rule and event-driven business process M&A
On the heels of IBM’s acquisition of Lombardi comes Progress Software’s acquisition of Savvion. The salient similarities are that IBM is adding BPM applications to its middleware stack as is Progress, at least with regard to its enterprise service bus offerings. More interesting is the relationship between Progress’ complex event processing software and Savvion’s BPM. Also of note is the vendor-provided integration of JBOSS Rules within Savvion versus the unrealized potential of IBM’s Ilog with respect to Lombardi.
We’ve written several times about the artificial distinction between CEP and BPM, their inevitable convergence, and the immature integration of business rules with business process management and event processing that inhibits knowledge-driven governance and decisioning. Continue reading “Rule and event-driven business process M&A”
Haley / ART syntax lives on in open-source Java rules
The ART syntax lives on in yet another product!
JBOSS Rules (formerly Drools) just described its imminent support for rules expressed in the CLIPS syntax here.
NASA derived CLIPS from the syntax of Inference Corporation’s Automated Reasoning Tool (ART) in the mid-80s. I designed and implemented the ART syntax with Chuck Williams on a team with Brad Allen and Mark Wright.
CLIPS didn’t have many of the features of ART (including an ATMS or backward chaining, for example), but it Continue reading “Haley / ART syntax lives on in open-source Java rules”