Event Transformation Services

In my last post, CEP Event Sources, I started a (short) list of event sources, both in theory and in practice, for complex event processing. There were some good comments and the list is evolving and improving.

Event transformations are used to convert inbound event objects to an outbound object type required by a transport layer, such as a JMS Message, or a stream, such as a market data format, or other event or feed handler.

Event transformations typically happen in the event preprocessing stage, of an application; but in a generalized architecture, events can be preprocessed throughout the event processing lifecycle. Multiple transformations can be combined, chained or piped together as required.

Below is a list of commonly used event transformations. Please feel free to comment as we add (or subtract) to (or from) the list.

Other Possible Transformations (not exhaustive)

  • Cryptographic Transformations
  • Encoding Transformations
  • CVS Transformations
  • Vendor Specific Transformations

Please contribute to the list with your comments.

Advertisements

5 Responses to Event Transformation Services

  1. Following on from my comment on your previous post, I think one interesting class of event transformation would be analog-to-digital. For example, automatic extraction of events from video (think CCTV in an airport or other transport system) or voice.

  2. Tim Bass says:

    Hi Richard,

    I agree.

    From a state-of-the-art perspective, it would be easier to publish an event from a security check point system that, either scans a passport ,or has a human enter the information into a system application, versus building an image recognition system that has 99.999… reliability of detecting an event.

    Detecting images from video is a signal processing application, and the signal processing application would then publish the event-object for other agents, like an analytical engine, to process.

    Thanks for visiting and contributing!

    Yours faithfully, Tim

  3. It is clearly important to understand the accuracy with which an event can be (a) captured and (b) transformed within a given system/environment. Video might be used to track a particular passenger, or merely to provide a warning that the number of passengers waiting for passport control has exceeded some safety level. There may be a trade-off between what is easier/cheaper for the system designer and what is easier/quicker for the human actors within the system. Scanning and data entry may slow down the system and cause longer queues for passport control.

    I believe it is important to characterize the event separately from the event-capture, and then give the system designer a choice between alternative event-capture mechanisms (based on such factors as accuracy, cost and system performance). The state-of-the-art in event-capture may improve over time, and we may wish to adopt new mechanisms as they become available, without this forcing us to alter the overall architecture of the system.

  4. Anil Datt says:

    Tim,

    Looking at the capabilities of Event Processing Language (EPL) where they can be used as filters prior to processing the Event can also be included as transformers. They lie beyond the boundary of “Transformations layer” using non-EPL, but lie just above the Event Processing.

    Anil Datt

  5. Tim Bass says:

    Hi Anil,

    Correct. Thanks for the second set of eyes on the list. I’ll add this right way.

    Yours faithfully, Tim

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: