Tracking change and innovation in the enterprise software development community
Terracotta:
Scale your
Apps w/ease
Offload the DB:
Learn More!
JProbe Freeware,
an Eclipse plug-in,
diagnoses
memory issues
quickly & easily.
QCon San Francisco
Nov 19-21:
+ 80 sessions & tracks
Register now
and Save $400!
IBM WebSphere
Virtualize apps
to lower costs,
Increase agility
Learn more!
The merger of Lawson and Intentia in 2006 left developers with an important problem to solve - the integration and presentation of legacy applications and business services that are constructed in Java, .NET, and other technologies. This case study looks under the hood at the new architecture at Lawson and how they got there.
JBoss Drools, an open-source business rules engine, recently reached version 4.0. InfoQ took the opportunity to learn more about JBoss Drools and its current and future capabilities.
Boris Lublinsky and Didier Le Tien discuss how business process engines and business rule engines differ, where their respective strengths are and when to use what in an SOA context. They discuss commonalities and differences between business rules and business processes and present some guidelines on positioning business rules in SOA implementation and appropriate usage of each technology.
Rule engines are a useful tool that can be used to externalize business logic, involve business users, or solve certain classes of problems in an efficient way. In this InfoQ Article, Geoffrey Wiseman explains what, when, and how to use rules engines along with his experiences applying them in finanicial services.
.jpg)
Boris Lublinsky and Didier Le Tien discuss how business process engines and business rule engines differ, where their respective strengths are and when to use what in an SOA context. They discuss commonalities and differences between business rules and business processes and present some guidelines on positioning business rules in SOA implementation and appropriate usage of each technology.
James Taylor looks at the challenge that arises when the new requirements are not really requirements at all, but new or changed business rules. Aren't business rules the same as requirements? Taylor says: no, not really; and looks at how to make an agile development processes work just as well for business rules as they do for other kinds of requirements.
For many developers, rule engines are buzzwords, or black boxes on an architectural diagram: something to be feared or admired from afar, but not understood. In this article, Geoffrey Wiseman shares his practical experience with rule engines and with Drools in particular to support in-market solutions for financial services.
