Panel: Event Processing Standards? - What? When? Why? How they are related to other standards?
Moderator: Roy Schulte, Gartner
Panelists:
- Adrian Paschke (RuleML)
- Bob Marcus (SRI)
- Chris Ferris (IBM)
- Louis Lovas (Progress/Apama)
- Paul Vincent (TIBCO)
Roy opens sharing Gartner taxonomy of relationships between Web Architecture, SOA and Event Processing. SOA & Web overlap in Web Oriented Architecture, SOA & Event Processing overlap in Event Driven SOA. (No overlap charted between Web & Event, but there probably is one.)
Next, Roy talks about how SOA adoption accelerated with WS* standards. As well, he points out important Web Standards such as HTTP, REST & Atom (maybe more, slide moved to fast).
Points out the neither WS* or Web standards address application portability of CEP. Nor, were they expect to.
Questions for panel:
- Are protocol standards for messaging important? If so, Atom, SOAP, WS-RM, WS-Eventing, WS-Notification, AMQP, DDS, other?
- Do we need standards for event schemas?
- (slide moved to quick)
- (slide moved to quick)
Paul Vincent, Tibco
What areas of interest?
- Model language standard
- Execution Semantics standard
- Middleware channel standard
- event payloads / DSLs
- Framework / Service standard
Tibco, what, when and why depend on customer interest/demand. Shows laundry list of current standards and activities that may apply.
Adrian Pashcke, RuleML
Shares another list of existing standards that may apply. Some standards overlap with Paul's list. Lots of functional overlap on and between the lists. Adrian is second of five panelists, I have a bad feeling about where this is going.
Bob Marcus, SRI
6 Points for Event Processing
- Explosion in EP applications caused by data deluge
- Cloud platform will be a major part of the solution for many users
- An enterprise cloud computing group has been formed which could provide a forum for Event Processing as a Service
- Specify data sources to monitor
- Specify QoS, resources to use
- Need a standard complex event definition language for user queries
Louis Lovas, Technical Fellow, Progress / Apama
Starts with the integration challenge, including many message protocols and many message semantics (data formats, business transaction/semantics), capital markets are fragmented -- racing to microsecond, leads to proprietary protocols, SOA standards abound and sensor devices have little standardization on data formats.
Standards lead to reduced implementation costs, improved vendor software tooling and specialized components for industries. Warns against blindly applying SOA standards to event processing. End up with bunch of JMS messages, not events.
"Language is most contentious issue facing EP industry. Streaming SQL does not equal CEP."
Louis throws another standard into the mix, STAC Benchmark council.
Chris Ferris, IBM
Chris asks, "are we ready to create standard?" Will standards created now allow products to be put in place for next 5-15 years? Is there a framework that can be developed now and extended over time?
Semantics will be the key. Dealing with information from organizations in which you (event processor) have no control. How to connect the dots between the various semantic schemes?
Q&A
1. What should EPTS do in respect to pushing requirements to standards organization? Is it time? Or, still too early? Should group be working on event format? Panel discussing origins of SOAP & WSDL and how 'ecosystem was created'. Now, I'm scared. Oh good, so is another panelist, calling out shift to REST because of WS* complexity.
Unfortunately, I need to cut out to catch my train. I'll ping Roy to learn about the panel outcome.
Leave a comment