|
|
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 SUNOS
dat_evd_resize
dat_evd_resize(3DAT) Direct Access Transport Library Functions dat_evd_resize(3DAT) NAME
dat_evd_resize - modify the size of the event queue of Event Dispatcher SYNOPSIS
cc [ flag... ] file... -ldat [ library... ] #include <dat/udat.h> DAT_RETURN dat_evd_resize( IN DAT_EVD_HANDLE evd_handle, IN DAT_COUNT evd_min_qlen ) PARAMETERS
evd_handle Handle for an instance of Event Dispatcher. evd_min_qlen New number of events the Event Dispatcher event queue must hold. DESCRIPTION
The dat_evd_resize() function modifies the size of the event queue of Event Dispatcher. Resizing of Event Dispatcher event queue should not cause any incoming or current events on the event queue to be lost. If the number of entries on the event queue is larger then the requested evd_min_qlen, the operation can return DAT_INVALID_STATE and not change an instance of Event Dispatcher RETURN VALUES
DAT_SUCCESS The operation was successful. DAT_INVALID_HANDLE The evd_handle parameter is invalid. DAT_INVALID_PARAMETER The evd_min_qlen parameter is invalid DAT_INSUFFICIENT_RESOURCES The operation failed due to resource limitations DAT_INVALID_STATE Invalid parameter. The number of entries on the event queue of the Event Dispatcher exceeds the requested event queue length. USAGE
This operation is useful when the potential number of events that could be placed on the event queue changes dynamically. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Standard: uDAPL, 1.1, 1.2 | +-----------------------------+-----------------------------+ |MT-Level |Unsafe | +-----------------------------+-----------------------------+ SEE ALSO
libdat(3LIB), attributes(5) SunOS 5.10 16 Jul 2004 dat_evd_resize(3DAT)