|
|
Master SOA Design Pattern Catalog
|
|
|
|

Rules Centralization (Erl)

|

Home > Inventory Centralization Patterns > Rules Centralization
|
|
How can business rules be abstracted and centrally governed?
|
|
|
|
|

Problem

The same business rules may apply across different business
services, leading to redundancy and governance challenges.
|
|

Solution

The storage and management of business rules are positioned
within a dedicated architectural extension from where they can
be centrally accessed and maintained.
|
|

Application

The use of a business rules management system or engine is
employed and accessed via system agents or a dedicated service.
|
 |
 |
 |

Impacts

Services are subjected to increased performance overhead, risk,
and architectural dependency.
|
|
|
|
|
|


|
|
Just two business rules can find their way into several different business services and, in this case, even a utility service. A global
change to either rule will therefore impact multiple services.
|
|
|
This page contains excerpts from:

SOA Design Patterns by Thomas Erl

Foreword by Grady Booch

With contributions from David Chappell, Jason Hogg, Anish Karmarkar, Mark Little, David Orchard, Satadru Roy, Thomas Rischbeck, Arnaud Simon, Clemens Utschig, Dennis Wisnosky, and others.

(ISBN: 0136135161, Hardcover, Full-Color, 400+ Illustrations, 865 pages)

For more information about this book, visit www.soabooks.com.
|
|