Technical Requirements of a CEP System

CEP systems must be able to receive and record events and identify patterns of these events and any related data. CEP systems must also handle temporal or time-based constraints, especially for handling the non-occurrence of events.

The following TIBCO BusinessEvents features satisfy these requirements:

  • A rich event model, incorporating event channels (for different event mechanisms, such as different types of messaging software) and destinations (for different types of events).
  • A pattern detection mechanism using a sophisticated, high performance, declarative rule engine.
  • A backing store for historical depth, and to enable use of more event data and entity data than can be persisted using memory cache technologies.

The following add-on products enrich the functionality:

  • A state model mechanism that allows entities to be described in terms of state and modelling of time-out events to handle the non-occurrence of events. (State modeling requires TIBCO BusinessEvents Data Modeling, purchased separately.)
  • Query features that enable retrieval of specific data from the data store or from the event stream as it arrives, using SQL-like object query language.
  • Pattern matching features that enable you to, for example, specify and identify the temporal order of event arrivals, and to correlate events across different event streams.
  • The ability to import and use entity data that is stored in various enterprise data stores.