This week I attended a meetup event (spi-nl) in Utrecht (The Netherlands) organized by Rubix which was dedicated to event processing. During this event one of my colleagues Joris Best gave a very good presentation in which he (among other things) explained the difference between Event Stream Processing (ESP) and Complex Event Processing (CEP). This presentation inspired me for this blog in which I will give a small definition on both Event Stream Processing (ESP) and Complex Event Processing (CEP) as I look at it. I know I am only pointing out the tip of the iceberg but nevertheless I wanted to share these thought with you. I will also give an example of TIBCO product dedicated to both types of analytics for those unfamiliar with the TIBCO product family.
ESP (Event Stream Processing)
“Continous querying” (applying mathematical and relational processing) on real-time data streams coming from disparate sources within a moving time window to reveal additional insight. ESP can also be used as a filtering mechanism to filter out unwanted noise in a certain stream of data before it enters the enterprise boundaries or being consumed by a CEP solution.
An example of a product is TIBCO StreamBase, a streaming analytics engine.
CEP (Complex Event Processing)
“Event-by-event” processing of events that may originate from a stream of data which combined (correlated) can reveal significant value to the business. One of the key features is a state model, an event-driven and rule-based mechanism for tracking and tracing entity lifecycle.
An example of a product is TIBCO BusinessEvents, a rule-based analytics engine.
Both of the products as mentioned above are part of TIBCO’s Fast Data Architecture and can be used in combination with TIBCO Live Datamart, which is a continuous query processor to provide advances visualizations that automatically push new results when data changes.