- #ORF09 An introduction to the RETE algorithm
- #ORF09 Playing With the Rules Presentation
- #ORF09 Rule Patterns and Features Presentation
- #ORF09 Early Alert System Presentation
- #ORF09 Engineer’s perspective on Rule Technology Keynote
- #ORF09 Enterprise Architecture Presentation
- #ORF09 Enterprise Architecture Presentation Part II
- #ORF09 Model Driven Approach for BRMS Presentation
- #ORF09 Production Rule Systems
- #ORF09 Graph Based Knowledge Bases and Rules Presentation
- #ORF09 Truth versus Useful Lies Presentation
- #ORF09 Automated Verification of rules Presentation
- #ORF09 Agile Business Rule Development Presentation
- #ORF09 Rule Classification First Presentation
- #ORF09 Rule Violation and Over-Constrained Problems Presentation
- #ORF09 Generating Rules from UML presentation
- #ORF09 What’s Different about Rules in CEP Presentation
- #ORF09 Measuring your Rules’ KPI Presentation
- #ORF09 Designing a System of Rule Based Agents Presentation
- #ORF09 Extending General Purpose Engines Presentation
- #ORF09 Programming Rules using a spreadsheet interface
- #ORF09 Practical and Modern RBE Presentation
- #ORF09 Temporal Reasoning Presentation
- #ORF09 Business Rules in the Cloud Presentation
- #ORF09 October Rules Fest Think Tank
- #ORF09 October Rules Fest Think Tank – Part II
- #ORF09 CLIPS implementation of RETE Presentation
- #ORF09 Complex Event Processing Models Presentation
- #ORF09 Distributed Programming with Agents Presentation
- #ORF09 making Parallelism Available to Rule Developers Presentation
Paul Vincent talked about Complex Event Processing (CEP).
What is Complex Event Processing? It is continuously processing events (asynchronous events) and passing it through to business events. One of the goals is to find patterns in the events from the “event cloud”.
The event cloud is the sum of all available events. There are also event streams. CEP uses pattern detections on the clouds and stream and their histories.
Problems solved: situational awareness, “sense and response” and “track and trace”.
From a technical point of view what does CEP need? Events are transient, so they have a limited time to live. Some are immutable, etc.
Event examples:
- SOA Service Requests
- Scans (RFID, etc.)
- Web requests
- Messages, Packets (networking world)
- Data streams (financial world)
Pattern matching of events is required. This should obviously resonate with the business rules community with pattern matching algorithms.
There is also a need for persistence and failover.
CEP Rules requires:
- Temporal awareness (General patterns, state patterns, event state patterns, object history patterns)
- A Simple Rule Model (similar to the PRR model) (Rulesets, Rules, variables, conditions, actions, events)
- Rule Types (Basic condition-action, Triggers Event-Condition-Action, Timers and schedulers, event lifecycle, state transition)
- Low latency and scalability
CEP uses State Models and State machines to implement the event life cycle.
Interesting presentation on CEP. I guess I will have to look at what products like Tibco and Drools Fusion offer for event processing.
Tags: Business Rules, Conferences, ORF09