Charles Young is talking about CEP.

He skims through the first couple of slides because CEP has been covered to some degree in earlier presentations.

CEP requires :

• Integration with Event Clouds
• Event Pattern Recognition
• Event Aggregation
• Performance & Scalability
• Tooling

CEP Agents are:

• Sense
• Deliver
• Adapt in
• Detect
• Reify
• Act
• Adapt out
• Relay

These are not the whole picture since we need to support multiple sources, etc.

The bulk of CEP technologies today are event stream processing engines.

Two approaches:

• Stream orientated approach
• Set-based approach

Some engines use Set-based operators:

• Stream to view
• View to view
• View to stream

There are a variety of ways to use “Select and Consume” strategy. There is a lot of complexity around that. In terms of context is about various ways to handle timestamps, temporal windows, template instantiation.

There are many “Event Pattern Languages”, but the details are not necessarily important, as long as the language supports what you are trying to do. (He lists some).

He then linked Rete to CEP in some detail. Rete can help for the optimization of the filtering portion of event stream processing.

Other issues:

• Event semantics (immutability)
• Temporal logic
• Selection and Consumption
• and 2 more I did not have time to write down

Why use Rete in CEP?

• Stream reasoning
• Bridging the gaps
  • e.g. Event Processing to Business Processes
  • Event Processing to Analytics

He then covered different models to using Rete in CEP

• Rete before Event Stream processing
• Rete after Event Stream Processing
• Hybrid agents
  • Event Stream Processing injecting events in between the alpha network and beta network of the Rete
  • Event Stream Processing injecting at the end of the Rete network

We need to bring Event Processing Networks closer to Enterprise Service Bus.