Book Image

Drools JBoss Rules 5.X Developer's Guide

By : Michal Bali
Book Image

Drools JBoss Rules 5.X Developer's Guide

By: Michal Bali

Overview of this book

<p>Writing business rules has always been a challenging task. Business rules tend to change often leading to a maintenance nightmare. This book shows you various ways to code your business rules using Drools, the open source Business Rules Management System.<br /><br />Drools JBoss Rules 5.X Developer's Guide shows various features of the Drools platform by walking the reader through several real-world examples. Each chapter elaborates on different aspects of the Drools platform. The reader will also learn about the inner workings of Drools and its implementation of the Rete algorithm.<br /><br />The book starts with explaining rule basics, then builds on this information by going through various areas like human readable rules, rules for validation, and stateful rules, using examples from the banking domain. A loan approval process example shows the use of the jBPM module. Parts of a banking fraud detection system are implemented with the Drools Fusion module which is the complex event processing part of Drools. Finally, more technical details are shown detailing the inner workings of Drools, the implementation of the ReteOO algorithm, indexing, node sharing, and partitioning.</p>
Table of Contents (22 chapters)
Drools JBoss Rules 5.X Developer's Guide
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Setting Up the Development Environment
Creating Custom Operators
Dependencies of Sample Application
Index

Architecture


From bottom to top, this sample application will consist of three layers: persistence, service, and presentation. It can be seen in the next figure. The persistence layer is responsible for storing objects in a database. Transactions guarantee consistency of the database and provide isolation between concurrent requests. The service layer represents the business logic of this application. It consists of the validation service, complex event processing (CEP) service, and loan approval service. Finally, the presentation layer uses these services to provide functionality to the users in a user friendly fashion.

Figure 1: Sample application architecture diagram

Please note that with some minor configuration changes, the service layer and presentation layer may be deployed on different physical servers and communicate over the network. With some more configuration changes, it is even possible to have multiple service or presentation layer deployments. This won't be covered in this...