EDA and BRM

For my school module Business Rule management (BRM) i need to write a paper. I’m planning to write a paper of the combination of BRM and EDA (event driven architecture). This combination is currently been used in a project in which I’m involved.

My hypotheses will be:

“Business Rules are necessary with the realization of an event driven architecture”

First i will try to explain the two concepts (BRM and EDA)

Event-driven architecture (EDA) is a software architecture pattern promoting the production, detection, consumption of, and reaction to events.

An event can be defined as “a significant change in state”. For example, when a consumer purchases a car, the car’s state changes from “for sale” to “sold”. A car dealer’s system architecture may treat this state change as an event to be produced, published, detected and consumed by various applications within the architecture.

This architectural pattern may be applied by the design and implementation of applications and systems which transmit events among loosely coupled software components and services. An event-driven system typically consists of event emitters (or agents) and event consumers (or sinks). Sinks have the responsibility of applying a reaction as soon as an event is presented. The reaction might or might not be completely provided by the sink itself. For instance, the sink might just have the responsibility to filter, transform and forward the event to another component or it might provide a self contained reaction to such event. The first category of sinks can be based upon traditional components such as message oriented middleware while the second category of sinks (self contained online reaction) might require a more appropriate transactional executive framework.

Building applications and systems around an event-driven architecture allows these applications and systems to be constructed in a manner that facilitates more responsiveness, because event-driven systems are, by design, more normalized to unpredictable and asynchronous environments.

Source: http://en.wikipedia.org/wiki/Event-driven_architecture

Business rules are abstractions of the policies and practices of a business organization. The Business Rules Approach is a development methodology where rules are in a form that is used by, but does not have to be embedded in, business process management systems.

The Business Rules Approach formalizes an enterprise’s critical business rules in a language that managers and technologists understand. Business rules create an unambiguous statement of what a business does with information to decide a proposition. The formal specification becomes information for process and rules engines to run.

Source: http://en.wikipedia.org/wiki/Business_rules_approach

 

A state that changes is something that must be a business rule (when is a car offer is made?). Next to that when an question is send for an calculation of a car, systems must react, but there are many options of this car sale, the car can be sold with different options and guaranties. Now you want all systems (dealer application, webapplication, etc.) to calculate the car price according to the same rules. That’s where BRM comes in. All systems that need to make complicated decisions will access a BRM engine which will calculate the price. In this example the know is separated from the flow. 

In traditional 3 layer applications this knowledge is programmed in the business layer of an application.

Categories: Architecture, Training Tags: , , ,
  1. February 12th, 2010 at 03:03 | #1

    Where are you from? Is it a secret? 🙂
    Thank you
    Edwas

  2. January 17th, 2011 at 21:55 | #2

    I love when you talk about this type of stuff in your posts. Perhaps could you continue to do this?

  3. February 9th, 2014 at 23:04 | #3

    Hello, of course this paragraph Head in the clouds, feet in the mud » EDA and BRM is in fact good and I have learned lot of things from it regarding blogging. thanks.

  1. No trackbacks yet.