Sponsored Content
Special Forums UNIX and Linux Applications Virtualization and Cloud Computing CEP as a Service (CEPaaS) with MapReduce on Amazon EC2 and Amazon S3 Post 302261746 by Linux Bot on Tuesday 25th of November 2008 01:08:53 PM
Old 11-25-2008
CEP as a Service (CEPaaS) with MapReduce on Amazon EC2 and Amazon S3

Tim Bass
11-25-2008 01:02 PM
Just as I was starting to worry that complex event processing community has been captured by RDBMS pirates off the coast of Somalia, I rediscovered a new core blackboard architecture component, Hadoop.

Hadoop is a framework for building applications on large commodity clusters while transparently providing applications with both reliability and data motion.* Hadoop implements* Map/Reduce, where an application is divided into many small components of work, each of which may be executed or re-executed on any node in the cluster.

There are a number of great articles on implementing Hadoop in the Amazon Elastic Computing Cloud (EC2), including this one, Running Hadoop MapReduce on Amazon EC2 and Amazon S3.* Hadoop provided the core component that permits a distributed agent-based architecture to become a manageable, simple-to-use service.** This, in turn, provides a framework, as a service, for solving complex distributed computing problems.

Another good article to read is Taking Massive Distributed Computing to the Common Man - Hadoop on Amazon EC2/S3. There is also a nice article on the Amazon EC2 on the Hadoop Wiki.

It is interesting to note that if you Google around you will find that the same RDBMS folks who have pirated the term “complex event processing” are some of the most vocal Hadoop critics. Further reading, however, you will see that most of the critical comments by the RDBMS crowd have been answered.* It is very interesting to see the same debate in the MapReduce community as in the CEP community, the difference of course is that the MapReduce community is much larger than the CEP community.

However, there should be no doubt in anyone’s mind that MapReduce and the Hadoop implementation provide a way to accomplish CEP.* It is very refreshing to see this emerging CEP architecture on the rise.

Stay tuned for much more information related to MapReduce and CEP.



Source...
 

3 More Discussions You Might Find Interesting

1. Virtualization and Cloud Computing

Running MySQL on Amazon EC2 with Elastic Block Store

Here is an excellent article on Running MySQL on Amazon EC2 with Elastic Block Store. Amazon Web Services Developer Connection : Running MySQL on Amazon EC2 with Elastic Block Store (0 Replies)
Discussion started by: Neo
0 Replies

2. Virtualization and Cloud Computing

Securing code in Amazon EC2

Hi All, I am facing a problem, regarding code security on EC2. We have created an AMI which contains our code in it, and need to bind the code to the AMI so that no one can take the code out of the AMI. Are there some ways to achieve this ??? (2 Replies)
Discussion started by: akshay61286
2 Replies

3. Virtualization and Cloud Computing

anyone running SELinux on amazon EC2?

Hi, Has anyone enabled SELinux on Amazon EC2? I tried to enable SELinux using a CentOS image, and the steps in the following post, but it didn't work!! Amazon Web Services Developer Community : Has anyone successfully enabled SELinux ... The steps i took: 1)I started with CentOS 5.3 base... (5 Replies)
Discussion started by: fun_indra
5 Replies
xsxp(n) 						    eXtremely Simple Xml Parser 						   xsxp(n)

__________________________________________________________________________________________________________________________________________________

NAME
xsxp - eXtremely Simple Xml Parser SYNOPSIS
package require Tcl 8.4 package require xml xsxp::parse xml xsxp::fetch pxml path ?part? xsxp::fetchall pxml_list path ?part? xsxp::only pxml tagname xsxp::prettyprint pxml ?chan? _________________________________________________________________ DESCRIPTION
This package provides a simple interface to parse XML into a pure-value list. It also provides accessor routines to pull out specific sub- tags, not unlike DOM access. This package was written for and is used by Darren New's Amazon S3 access package. This is pretty lame, but I needed something like this for S3, and at the time, TclDOM would not work with the new 8.5 Tcl due to version number problems. In addition, this is a pure-value implementation. There is no garbage to clean up in the event of a thrown error, for example. This sim- plifies the code for sufficiently small XML documents, which is what Amazon's S3 guarantees. Copyright 2006 Darren New. All Rights Reserved. NO WARRANTIES OF ANY TYPE ARE PROVIDED. COPYING OR USE INDEMNIFIES THE AUTHOR IN ALL WAYS. This software is licensed under essentially the same terms as Tcl. See LICENSE.txt for the terms. COMMANDS
The package implements five rather simple procedures. One parses, one is for debugging, and the rest pull various parts of the parsed doc- ument out for processing. xsxp::parse xml This parses an XML document (using the standard xml tcllib module in a SAX sort of way) and builds a data structure which it returns if the parsing succeeded. The return value is referred to herein as a "pxml", or "parsed xml". The list consists of two or more ele- ments: o The first element is the name of the tag. o The second element is an array-get formatted list of key/value pairs. The keys are attribute names and the values are attribute values. This is an empty list if there are no attributes on the tag. o The third through end elements are the children of the node, if any. Each child is, recursively, a pxml. o Note that if the zero'th element, i.e. the tag name, is "%PCDATA", then the attributes will be empty and the third element will be the text of the element. In addition, if an element's contents consists only of PCDATA, it will have only one child, and all the PCDATA will be concatenated. In other words, this parser works poorly for XML with elements that contain both child tags and PCDATA. Since Amazon S3 does not do this (and for that matter most uses of XML where XML is a poor choice don't do this), this is probably not a serious limitation. xsxp::fetch pxml path ?part? pxml is a parsed XML, as returned from xsxp::parse. path is a list of element tag names. Each element is the name of a child to look up, optionally followed by a hash ("#") and a string of digits. An empty list or an initial empty element selects pxml. If no hash sign is present, the behavior is as if "#0" had been appended to that element. (In addition to a list, slashes can separate subparts where convenient.) An element of path scans the children at the indicated level for the n'th instance of a child whose tag matches the part of the ele- ment before the hash sign. If an element is simply "#" followed by digits, that indexed child is selected, regardless of the tags in the children. Hence, an element of "#3" will always select the fourth child of the node under consideration. part defaults to "%ALL". It can be one of the following case-sensitive terms: %ALL returns the entire selected element. %TAGNAME returns lindex 0 of the selected element. %ATTRIBUTES returns index 1 of the selected element. %CHILDREN returns lrange 2 through end of the selected element, resulting in a list of elements being returned. %PCDATA returns a concatenation of all the bodies of direct children of this node whose tag is %PCDATA. It throws an error if no such children are found. That is, part=%PCDATA means return the textual content found in that node but not its children nodes. %PCDATA? is like %PCDATA, but returns an empty string if no PCDATA is found. For example, to fetch the first bold text from the fifth paragraph of the body of your HTML file, xsxp::fetch $pxml {html body p#4 b} %PCDATA xsxp::fetchall pxml_list path ?part? This iterates over each PXML in pxml_list (which must be a list of pxmls) selecting the indicated path from it, building a new list with the selected data, and returning that new list. For example, pxml_list might be the %CHILDREN of a particular element, and the path and part might select from each child a sub-ele- ment in which we're interested. xsxp::only pxml tagname This iterates over the direct children of pxml and selects only those with tagname as their tag. Returns a list of matching ele- ments. xsxp::prettyprint pxml ?chan? This outputs to chan (default stdout) a pretty-printed version of pxml. BUGS, IDEAS, FEEDBACK This document, and the package it describes, will undoubtedly contain bugs and other problems. Please report such in the category amazon- s3 of the Tcllib SF Trackers [http://sourceforge.net/tracker/?group_id=12883]. Please also report any ideas for enhancements you may have for either package and/or documentation. KEYWORDS
dom, parser, xml CATEGORY
Text processing COPYRIGHT
Copyright (c) Copyright 2006 Darren New. All Rights Reserved. amazon-s3 1.0 xsxp(n)
All times are GMT -4. The time now is 11:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy