|
|
Sponsored Content
Special Forums
UNIX and Linux Applications
Virtualization and Cloud Computing
Cloud Event Processing vs Event Cloud Processing?
Post 302278566 by Linux Bot on Tuesday 20th of January 2009 04:00:02 PM
01-20-2009
Cloud Event Processing vs Event Cloud Processing?
vincent
01-20-2009 05:51 AM
Interesting to see the huge interest in Cloud Computing. David Luckham’s complexevents.com just referenced one of several recent Infoworld articles and blogs that attempt to define the term. Another compares the buzz to past excitements - remember Application Service Provider and Software As A Service? But Clouds are of direct interest to the Complex Event Processing community: CEP is, afterall, about processing clouds of events.
Just to be clear…
1. Complex Event Processing is another term for Event Cloud Processing: processing clouds of events, which may include multiple event streams of course.
2. Cloud-based Event Processing is where some event processing application is put into a closed / corporate, or public / distributed, cloud computing environment. Event latency and event store latency will be major considerations here.
It’s interesting to compare “cloud computing” with more conventional advances in distributed corporate IT. TIBCO BusinessEvents, for example, provides an “event cloud processing” (aka CEP!) platform that includes both the event processing and data cache agents. Will this ever be requested, or offered, as a cloud service by TIBCO or a TIBCO partner? Possibly. Application domains for this might be the interface between the social network and commercial IT worlds - consider things like medical drug programs, healthcare data collection, and so forth. We’ll let you know if and when it happens…
Source...
01-20-2009 05:51 AM
Interesting to see the huge interest in Cloud Computing. David Luckham’s complexevents.com just referenced one of several recent Infoworld articles and blogs that attempt to define the term. Another compares the buzz to past excitements - remember Application Service Provider and Software As A Service? But Clouds are of direct interest to the Complex Event Processing community: CEP is, afterall, about processing clouds of events.
Just to be clear…
1. Complex Event Processing is another term for Event Cloud Processing: processing clouds of events, which may include multiple event streams of course.
2. Cloud-based Event Processing is where some event processing application is put into a closed / corporate, or public / distributed, cloud computing environment. Event latency and event store latency will be major considerations here.
It’s interesting to compare “cloud computing” with more conventional advances in distributed corporate IT. TIBCO BusinessEvents, for example, provides an “event cloud processing” (aka CEP!) platform that includes both the event processing and data cache agents. Will this ever be requested, or offered, as a cloud service by TIBCO or a TIBCO partner? Possibly. Application domains for this might be the interface between the social network and commercial IT worlds - consider things like medical drug programs, healthcare data collection, and so forth. We’ll let you know if and when it happens…
Source...
|
|
We Also Found This Discussion For You
1. Virtualization and Cloud Computing
Tim Bass
Thu, 15 Nov 2007 23:55:07 +0000
*I predict we may experience less*debates*on the use of the term “event cloud”*related to*CEP in the future, now that both IBM and Google* have made announcements about “cloud computing” and “computing cloud”, IBM Turning Data Centers Into ‘Computing... (0 Replies)
Discussion started by: Linux Bot
0 Replies
LEARN ABOUT DEBIAN
sensor
Sensor(3I) Sensor(3I) NAME
Sensor - describe input interest SYNOPSIS
#include <InterViews/sensor.h> DESCRIPTION
A sensor specifies a set of input events to catch. PUBLIC OPERATIONS
Sensor() Create a new sensor that initially will not catch any events. virtual void motion(boolean) Specify the sensor should (parameter is true) or should not (parameter is false) catch pointer motion events. virtual boolean motion() Return whether the sensor is catching pointer motion events. virtual void key(boolean) Specify the sensor should (parameter is true) or should not (parameter is false) catch keyboard events. virtual boolean key() Return whether the sensor is catching keyboard events. virtual void button(boolean, PointerButton = Event::any) Specify the sensor should (parameter is true) or should not (parameter is false) catch button events. The pointer button may spec- ify a particular button or Event::any (meaning all button events). virtual boolean button(PointerButton = Event::any) Return whether the sensor is catching button events. The pointer button may specify a particular button or Event::any (meaning any of the buttons). virtual boolean caught(Event&) Return whether the sensor is catching the given event. void Catch(EventType) Express interest in a particular type of event. This function is provided solely for backward compatibility and will be removed in a future version. void CatchButton(EventType, int) Express interest in a particular type of button event for a specific button. This function is provided solely for backward compati- bility and will be removed in a future version. void Ignore(EventType) Remove interest in a particular type of event. This function is provided solely for backward compatibility and will be removed in a future version. void IgnoreButton(EventType, int) Remove interest in a particular type of button event for a specific button. This function is provided solely for backward compati- bility and will be removed in a future version. SEE ALSO
Event(3I) InterViews Reference Manual Sensor(3I)