|
|
Sponsored Content
Special Forums
UNIX and Linux Applications
Virtualization and Cloud Computing
No bottlenecks in Complex Event Processing for Real-time BI
Post 302226447 by Linux Bot on Tuesday 19th of August 2008 04:40:03 AM
08-19-2008
No bottlenecks in Complex Event Processing for Real-time BI
vincent
08-18-2008 04:54 PM
A few BI-related posts show how CEP and CEP-related thinking is starting to trickle into conventional thinking on Business Intelligence.
First off, Intelligent Enterprise reports on some solutions to the problems of using data warehouses for real-time BI. Note that the solutions offered include Event Stream Processing (although why Forrester references ESP instead of CEP is a mystery only known to the analyst who authored this report - unless there is an expectation that just simple streamed correlations can be done in real-time analytics?) [*1].
Secondly,* Jerry Held relates in 2 articles how cloud computing will “save the day” for BI. In a nutshell, Jerry’s hypothesis is that a lack of cheap distributed computing resources are what is holding back BI, and clouds of massively parallel operations on huge datasets will be BI’s saviours. Jerry, methinks, is ahead of his time, as I can’t see data warehouses migrating to the clouds without large doses of security provisions and even cheaper bandwidth. But certainly the idea of highly parallel and scalable event+data processing operations is here today…
Notes:
[1] IE also suggests “informational fabric” for real-time BI. This is “the real-time in memory, distributed caching infrastructure embedded in a service-oriented architecture or enterprise service bus for analytic and transactional apps.” This is also CEP-relevant - the TIBCO BusinessEvents CEP platform includes such a data grid.
Source...
08-18-2008 04:54 PM
A few BI-related posts show how CEP and CEP-related thinking is starting to trickle into conventional thinking on Business Intelligence.
First off, Intelligent Enterprise reports on some solutions to the problems of using data warehouses for real-time BI. Note that the solutions offered include Event Stream Processing (although why Forrester references ESP instead of CEP is a mystery only known to the analyst who authored this report - unless there is an expectation that just simple streamed correlations can be done in real-time analytics?) [*1].
Secondly,* Jerry Held relates in 2 articles how cloud computing will “save the day” for BI. In a nutshell, Jerry’s hypothesis is that a lack of cheap distributed computing resources are what is holding back BI, and clouds of massively parallel operations on huge datasets will be BI’s saviours. Jerry, methinks, is ahead of his time, as I can’t see data warehouses migrating to the clouds without large doses of security provisions and even cheaper bandwidth. But certainly the idea of highly parallel and scalable event+data processing operations is here today…
Notes:
[1] IE also suggests “informational fabric” for real-time BI. This is “the real-time in memory, distributed caching infrastructure embedded in a service-oriented architecture or enterprise service bus for analytic and transactional apps.” This is also CEP-relevant - the TIBCO BusinessEvents CEP platform includes such a data grid.
Source...
|
|
LEARN ABOUT LINUX
coseventchanneladmin
CosEventChannelAdmin(3erl) Erlang Module Definition CosEventChannelAdmin(3erl) NAME
CosEventChannelAdmin - The CosEventChannelAdmin defines a set if event service interfaces that enables decoupled asynchronous communica- tion between objects and implements generic (untyped) version of the OMG COSS standard event service. DESCRIPTION
The event service defines two roles for objects: the supplier role and the consumer role. Suppliers supply event data to the event channel and consumers receive event data from the channel. Suppliers do not need to know the identity of the consumers, and vice versa. Consumers and suppliers are connected to the event channel via proxies, which are managed by ConsumerAdmin and SupplierAdmin objects. There are four general models of communication. These are: * The canonical push model. It allows the suppliers of events to initiate the transfer of event data to consumers. Event channels play the role of Notifier . Active suppliers use event channel to push data to passive consumers registered with the event channel. * The canonical pull model. It allows consumers to request events from suppliers. Event channels play the role of Procure since they pro- cure events on behalf of consumers. Active consumers can explicitly pull data from passive suppliers via the event channels. * The hybrid push/pull model. It allows consumers request events queued at a channel by suppliers. Event channels play the role of Queue . Active consumers explicitly pull data deposited by active suppliers via the event channels. * The hybrid pull/push model. It allows the channel to pull events from suppliers and push them to consumers. Event channels play the role of Intelligent agent . Active event channels can pull data from passive suppliers to push it to passive consumers. To get access to all definitions, e.g., exceptions, include necessary hrl files by using: -include_lib("cosEvent/include/*.hrl"). There are seven different interfaces supported in the service: * ProxyPushConsumer * ProxyPullSupplier * ProxyPullConsumer * ProxyPushSupplier * ConsumerAdmin * SupplierAdmin * EventChannel Ericsson AB cosEvent 2.1.10 CosEventChannelAdmin(3erl)