vincent
Mon, 07 Jul 2008 12:26:30 +0000
Continuing on with the Distributed Event Based Systems conference, its quite surprising that the presentations on event transmission (aka intelligent middleware, content-based pub-sub, clustering pub-sub nodes for performance, secure pub-sub etc etc) and of event processing (CEP, ESP, Bayes/rules/uncertainty/queries etc etc) are not in different “streams”, given they have different audiences. From a CEP perspective, middleware is certainly necessary (and for TIBCO, er, pretty relevant), but our interest is more on what to do with events, not worry about how they arrive.
Having said that, there is clearly a connection between “intelligent / optimal distribution of events” and “distributed (complex) event processing”. And “dynamic routing” implies “intelligent nodes” that are, in effect, limited event processing agents. So the concepts are connected, although the R&D goals may, today, differ (e.g. middleware: routing resilience, performance and scaleability; CEP: event processing scaleability, performance and resilience…).
A few observations were:

• In a presentation on gaming events, the definition of Event included an “obsolete” attribute, used to indicate an event whose existance is made “irrelevant” by some subsequent event(s). I’m not sure this is a generic attribute of all events, though - the event still happened, and could be correlated (for example to identify the speed at which such events become obscolete). So this is probably useful in some contexts, and not others.
• An event metamodel was presented by the University of Waterloo in Canada, which was much more comprehensive (/complex) that the definition we use in TIBCO BusinessEvents (for Event Processing). But their goal, to make “event” a first class entity, is shared by the OMG EMP team, with whom the Waterloo group should probably be collaborating.

Source...