Event processing architectural patterns

In this section, we will show how the different components of the architecture discussed before can be added together into architectural patterns in order to support certain use cases. We have identified the following patterns:

• Standalone event processing
• Event processing in front of BPM and/or SOA
• Decoupling processes/services through business events (potentially including some event processing)
• Analyzing BPM process behavior with event processing

These patterns are now explained together with a use case in our RYLC system.

Architectural pattern 1 – standalone event processing

In this pattern, event processing is used to implement a solution that captures and refines high-volume event data that arrives from other systems (either internal or external sources) and makes it available for later analytics. External sources can be a lot of things, from the so-called Internet of Things to social media streams. The purpose of such applications of event processing...