« Legacy modernization, business rules and offshore development | Main | How DO decision services get data? »

Opher Etzion had a nice post today - More thoughts on Rules in the context of Event Processing - in which he discussed different ways in which rules apply to event processing. He identifies 5 different areas in which rules can be used as part of an event processing approach and, in the process, reiterates something I often find I have to explain to people. Just because a product or approach uses "rules" (declarative statements of intent) does not mean that it is all you need to take a rules-based or decision-centric approach. In particular I like the fact that he drew a distinction between routing/transformation/validation/orchestration of events and "Intelligent Event Processing." It is this last that is the realm of enterprise decision management and where a coordinated approach to managing of decisions, typically using both business rules and predictive analytics, really pays off. These decisions are typically business decisions that are not tightly coupled to the specifics of your current systems or low-level events. While a business rules management system might well be useful for managing all the rules involved in event processing, probably it makes more sense to manage those rules tightly coupled to the definitions of events in the event processing environment. Once you get into broader business or enterprise decisions, then you need to think about managing those decisions so that they are not so tied to a particular architecture.
Some other posts you might find useful on this blog:

• Complex Event Processing - not just rules
• Decision management is critical to event driven architecture
• Predictive analytics go deeper
• Business rules, routing rules, event rules

Posted by jtaylor in Business Rules • Decision Technologies • Event Processing • Predictive Analytics |Digg This|Add to del.icio.us

Trackback Pings

TrackBack URL for this entry:
http://www.ebizq.net/mt/mt-tb.cgi/3056