Sponsored Content
Special Forums News, Links, Events and Announcements Complex Event Processing RSS News The Fallacy of Self-Fulfilling CEP Use Case Studies Post 302222261 by Linux Bot on Wednesday 6th of August 2008 11:50:02 AM
Old 08-06-2008
The Fallacy of Self-Fulfilling CEP Use Case Studies

Neo
08-06-2008 08:30 AM
I am back at the glaring computer screen*after a day in Lamphun, Northern Thailand, hanging out will my friends who are preparing for a Bonsai tree competition.**I spent the day*eating Thai and Chinese food and relaxing in a lounge chair under imported blue palm trees with the sound of exotic birds making background music to keep me entertained.

Back to CEP and EPTS, there are folks*who appear to believe*they may*define “CEP” by the current use cases from self-described CEP vendors. Frankly speaking, I am puzzled by the bottom-up approach.

The*bottom-up approach*is a bit like saying “We have a lot of prototype rockets being built, so let’s define the future of space travel based on the prototypes!”

It really makes little sense, at least to me,*to attempt to define CEP based on what the current generation products (self-described CEP products) are capable of doing.***

From my persective, it*would*be more*beneficial*to customers*to define the types of complex events*(and situations)*businesses need to detect in real-time and*match the technologies and solution architectures*to detect those events, in real-time, with high confidence.

A lot of this “top down thinking” has been already done.

IT businesses need to detect operational threats and problems, and be able to pinpoint, with very high accuracy, where the problem is in a complex network, for example.* This problem remains mostly*unsolved with a very*low sigaal-to-noise ratio.

Also, most*businesses*would like*to detect fraud and other criminal activity on their network before*the activities*adversely*impacts their business.** This*problem remains unsolved for most companies.

Scientific researchers*seek*models of weather, epidemiology, and so much more; and they need event processing solutions to obtain situational knowledge into current events and predict future ones.* We know how difficult predicting the weather can be!

Folks on the ground need to model urban traffic as events and design better event-driven traffic models and solutions.

The list of important event processing challenges we face go on and on.**

While I see some merit in the bottom-up approach, it is better for users to define what are practical “complex event” related problems and then look for the solutions, vs. define the solution and then look for the problem.

From a strategic perspective,* self-fulfilling CEP use case studies are interesting, but they should not limit the vision, definition, and future of processing complex events.



Source...
 

We Also Found This Discussion For You

1. Shell Programming and Scripting

How many studies have unequal values for each pair?

I have several Studies (s) which has points (p) having Values (v). My goal is to determine for each pair of points, how many studies have different values ( if available ). Study Point Value 1 p1 value1 1 p2 value2 1 p3 value1 1 p4 value3 1 p5 value3 2 p2 value1 2 p4 value1 3 p1 value1... (5 Replies)
Discussion started by: senhia83
5 Replies
Hash::Case::Upper(3pm)					User Contributed Perl Documentation				    Hash::Case::Upper(3pm)

NAME
Hash::Case::Upper - native hash with enforced lower cased keys INHERITANCE
Hash::Case::Upper is a Hash::Case is a Tie::StdHash SYNOPSIS
use Hash::Case::Upper; tie my(%uchash), 'Hash::Case::Upper'; $uchash{StraNGeKeY} = 3; print keys %uchash; # STRANGEKEY DESCRIPTION
Hash::Case::Upper extends Hash::Case, which lets you play various trics with hash keys. In this implementation, the fake hash is case insensitive and the keys stored in upper-case. METHODS
Constructors $obj->addHashData(HASH) See "Constructors" in Hash::Case $obj->addPairs(PAIRS) See "Constructors" in Hash::Case $obj->setHash(HASH) See "Constructors" in Hash::Case tie(HASH, 'Hash::Case::Upper', [VALUES,] OPTIONS) Define HASH to have only upper cased keys. The hash is initialized with the VALUES, specified as ref-array or ref-hash. Currently, there are no OPTIONS defined. SEE ALSO
This module is part of Hash-Case distribution version 1.02, built on March 09, 2012. Website: http://perl.overmeer.net/hash-case/ LICENSE
Copyrights 2002-2003,2007-2012 by Mark Overmeer. For other contributors see ChangeLog. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. See http://www.perl.com/perl/misc/Artistic.html perl v5.14.2 2012-03-09 Hash::Case::Upper(3pm)
All times are GMT -4. The time now is 11:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy