 <?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: OMG CEP Standards event: what standards?</title>
	<atom:link href="http://tibcoblogs.com/cep/index.php/2008/03/13/omg-cep-standards-event-what-standards/feed/" rel="self" type="application/rss+xml" />
	<link>http://tibcoblogs.com/cep/2008/03/13/omg-cep-standards-event-what-standards/</link>
	<description>Complex Event Processing (CEP)</description>
	<pubDate>Tue, 16 Mar 2010 06:09:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Complex Event Processing (CEP) Blog &#187; CEP sessions at the OMG Real-Time July 08 workshop</title>
		<link>http://tibcoblogs.com/cep/2008/03/13/omg-cep-standards-event-what-standards/comment-page-1/#comment-207</link>
		<dc:creator>Complex Event Processing (CEP) Blog &#187; CEP sessions at the OMG Real-Time July 08 workshop</dc:creator>
		<pubDate>Mon, 21 Jul 2008 18:01:06 +0000</pubDate>
		<guid isPermaLink="false">http://tibcoblogs.com/cep/2008/03/13/omg-cep-standards-event-what-standards/#comment-207</guid>
		<description>[...] products&#8221; to avoid vendor lock-in, even though the presenter (who had attended the OMG CEP standards event in March) recognized there was no compelling business case for the smaller vendors to develop such [...]</description>
		<content:encoded><![CDATA[<p>[...] products&#8221; to avoid vendor lock-in, even though the presenter (who had attended the OMG CEP standards event in March) recognized there was no compelling business case for the smaller vendors to develop such [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vincent</title>
		<link>http://tibcoblogs.com/cep/2008/03/13/omg-cep-standards-event-what-standards/comment-page-1/#comment-115</link>
		<dc:creator>vincent</dc:creator>
		<pubDate>Wed, 19 Mar 2008 22:12:40 +0000</pubDate>
		<guid isPermaLink="false">http://tibcoblogs.com/cep/2008/03/13/omg-cep-standards-event-what-standards/#comment-115</guid>
		<description>Thanks Angelo: I'm not sure how (1) is more than what conventional pub-sub provides, although the SQL query mechanism in theory means you could offset some filtering and queries to the DDS middleware. Which is your point (2) I believe, and is also subject to academic research like at Univ of Toronto (see last years EPTS Meeting). (3) to (5) make perfect sense, although I can't comment on whether DDS is better or worse than other solutions in this space.</description>
		<content:encoded><![CDATA[<p>Thanks Angelo: I&#8217;m not sure how (1) is more than what conventional pub-sub provides, although the SQL query mechanism in theory means you could offset some filtering and queries to the DDS middleware. Which is your point (2) I believe, and is also subject to academic research like at Univ of Toronto (see last years EPTS Meeting). (3) to (5) make perfect sense, although I can&#8217;t comment on whether DDS is better or worse than other solutions in this space.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Angelo Corsaro</title>
		<link>http://tibcoblogs.com/cep/2008/03/13/omg-cep-standards-event-what-standards/comment-page-1/#comment-114</link>
		<dc:creator>Angelo Corsaro</dc:creator>
		<pubDate>Wed, 19 Mar 2008 17:31:49 +0000</pubDate>
		<guid isPermaLink="false">http://tibcoblogs.com/cep/2008/03/13/omg-cep-standards-event-what-standards/#comment-114</guid>
		<description>Hello Paul,

First of all, I enjoyed your presentation at the CEP workshop. That said, I have  a few comments on your wander about the two DDS presentations. As showcased during the Workshop, DDS is the "perfect" transport for CEP engines for the following reasons, (1) it is extremely natural to map CEP events to DDS Topics, especially considering DDS support for relational data modeling, (2) DDS supports some event processing capabilities which could be used by CEP engines to off-load some of the filtering to the middleware, thus ensuring that only relevant events are delivered to the CEP in first place--thus more relevant events are processed overall! (3) DDS has unparalleled support for QoS, which allow to control temporal properties,  availability, persistence, reliability, etc., of data, (4) OMG DDS has on-the-wire interoperability, i.e., implementation from different vendors can speak to each other, and (5) it is very high throughput and low latency, meaning that leading DDS implementations can easily cope with Millions of messages per seconds, while retaining extra low  latency and jitter.

Moreover, leading vendors provide integration with both on-memory data bases as well as RDBMS such as Oracle, MySQL, etc., (this means that you could use DDS to connect to fully transparently and two way to the a DB), as well as security solutions.

In summary, DDS is the ideal transport for any application that has to stream and process in real-time huge amount of data and "make sense" of them in real-time. As you very well know, several examples of such applications are found in Financial Markets, Defense, SCADA, etc.</description>
		<content:encoded><![CDATA[<p>Hello Paul,</p>
<p>First of all, I enjoyed your presentation at the CEP workshop. That said, I have  a few comments on your wander about the two DDS presentations. As showcased during the Workshop, DDS is the &#8220;perfect&#8221; transport for CEP engines for the following reasons, (1) it is extremely natural to map CEP events to DDS Topics, especially considering DDS support for relational data modeling, (2) DDS supports some event processing capabilities which could be used by CEP engines to off-load some of the filtering to the middleware, thus ensuring that only relevant events are delivered to the CEP in first place&#8211;thus more relevant events are processed overall! (3) DDS has unparalleled support for QoS, which allow to control temporal properties,  availability, persistence, reliability, etc., of data, (4) OMG DDS has on-the-wire interoperability, i.e., implementation from different vendors can speak to each other, and (5) it is very high throughput and low latency, meaning that leading DDS implementations can easily cope with Millions of messages per seconds, while retaining extra low  latency and jitter.</p>
<p>Moreover, leading vendors provide integration with both on-memory data bases as well as RDBMS such as Oracle, MySQL, etc., (this means that you could use DDS to connect to fully transparently and two way to the a DB), as well as security solutions.</p>
<p>In summary, DDS is the ideal transport for any application that has to stream and process in real-time huge amount of data and &#8220;make sense&#8221; of them in real-time. As you very well know, several examples of such applications are found in Financial Markets, Defense, SCADA, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: In the names of CEP and BPM &#171; Commercial Intelligence</title>
		<link>http://tibcoblogs.com/cep/2008/03/13/omg-cep-standards-event-what-standards/comment-page-1/#comment-112</link>
		<dc:creator>In the names of CEP and BPM &#171; Commercial Intelligence</dc:creator>
		<pubDate>Fri, 14 Mar 2008 15:30:05 +0000</pubDate>
		<guid isPermaLink="false">http://tibcoblogs.com/cep/2008/03/13/omg-cep-standards-event-what-standards/#comment-112</guid>
		<description>[...] of discussions with others on this over the interim until today&#8217;s posts by Paul Vincent, summing up an OMG meeting in Washington, DC, and Sandy Kelmsley&#8217;s comments on a survey of 590 business [...]</description>
		<content:encoded><![CDATA[<p>[...] of discussions with others on this over the interim until today&#8217;s posts by Paul Vincent, summing up an OMG meeting in Washington, DC, and Sandy Kelmsley&#8217;s comments on a survey of 590 business [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
