[jboss-svn-commits] JBL Code SVN: r25005 - labs/jbossrules/trunk/drools-docs/drools-docs-fusion/src/main/docbook/en-US/Chapter-Introduction.
jboss-svn-commits at lists.jboss.org
jboss-svn-commits at lists.jboss.org
Thu Jan 29 21:15:50 EST 2009
Author: tirelli
Date: 2009-01-29 21:15:50 -0500 (Thu, 29 Jan 2009)
New Revision: 25005
Modified:
labs/jbossrules/trunk/drools-docs/drools-docs-fusion/src/main/docbook/en-US/Chapter-Introduction/Section-ComplexEventProcessing.xml
labs/jbossrules/trunk/drools-docs/drools-docs-fusion/src/main/docbook/en-US/Chapter-Introduction/Section-DroolsFusion.xml
Log:
wokring on docs
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-fusion/src/main/docbook/en-US/Chapter-Introduction/Section-ComplexEventProcessing.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-fusion/src/main/docbook/en-US/Chapter-Introduction/Section-ComplexEventProcessing.xml 2009-01-30 00:46:00 UTC (rev 25004)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-fusion/src/main/docbook/en-US/Chapter-Introduction/Section-ComplexEventProcessing.xml 2009-01-30 02:15:50 UTC (rev 25005)
@@ -9,19 +9,19 @@
<title>Complex Event Processing</title>
<para>Although several tries were made, there isn't up to date any broadly
- accepted definition on the term Complex Event Processing. The term Event
- by itself is frequently overloaded and used to refer to
- several different things, depending on the context it is used. Defining
- terms is not the goal of this guide and as so, lets adopt a loose definition
- that, although not formal, will allow us to proceed with a common
- understanding.</para>
+ accepted definition on the term Complex Event Processing. The term Event by
+ itself is frequently overloaded and used to refer to several different
+ things, depending on the context it is used. Defining terms is not the goal
+ of this guide and as so, lets adopt a loose definition that, although not
+ formal, will allow us to proceed with a common understanding.</para>
<para>So, in the scope of this guide:</para>
<important>
- <para><indexterm><primary>Event</primary></indexterm>
- <emphasis role="bold">Event</emphasis>, is a record of a significant
- change of state in the application domain.</para>
+ <para><indexterm>
+ <primary>Event</primary>
+ </indexterm> <emphasis role="bold">Event</emphasis>, is a record of a
+ significant change of state in the application domain.</para>
</important>
<para>For instance, on a Stock Broker application, when a sell operation is
@@ -64,17 +64,33 @@
briefly described as the following quote from Wikipedia:</para>
<important>
- <para>"<indexterm><primary>Complex Event Processing</primary></indexterm>
- <emphasis role="bold">Complex Event Processing</emphasis>, or CEP,
- is primarily an event processing concept that deals with the task of
- processing multiple events with the goal of identifying the meaningful
- events within the event cloud. CEP employs techniques such as detection of
- complex patterns of many events, event correlation and abstraction, event
- hierarchies, and relationships between events such as causality,
- membership, and timing, and event-driven processes."</para>
+ <blockquote>
+ <attribution><ulink
+ url="http://en.wikipedia.org/wiki/Complex_event_processing">
+ <citetitle>wikipedia</citetitle>
+ </ulink></attribution>
+
+ <para>"<indexterm>
+ <primary>Complex Event Processing</primary>
+ </indexterm> <emphasis role="bold">Complex Event
+ Processing</emphasis>, or CEP, is primarily an event processing concept
+ that deals with the task of processing multiple events with the goal of
+ identifying the meaningful events within the event cloud. CEP employs
+ techniques such as detection of complex patterns of many events, event
+ correlation and abstraction, event hierarchies, and relationships
+ between events such as causality, membership, and timing, and
+ event-driven processes."</para>
+ </blockquote>
</important>
- <para>In other words, CEP is about detecting and selecting the interesting
- events (and only them), finding their relationships and infering new data from them
- and their relationships.</para>
+ <para>In other words, CEP is about detecting and selecting the interesting
+ events (and only them) from an event cloud, finding their relationships and
+ infering new data from them and their relationships.</para>
+
+ <note><para>For the remaining of this guide, we will use the terms
+ <emphasis role="bold">Complex Event Processing</emphasis>
+ and <emphasis role="bold">CEP</emphasis> as a broad reference for any of
+ the related technologies
+ and techniques, including but not limited to, CEP, Complex Event Processing,
+ ESP, Event Stream Processing and Event Processing in general.</para></note>
</section>
Modified: labs/jbossrules/trunk/drools-docs/drools-docs-fusion/src/main/docbook/en-US/Chapter-Introduction/Section-DroolsFusion.xml
===================================================================
--- labs/jbossrules/trunk/drools-docs/drools-docs-fusion/src/main/docbook/en-US/Chapter-Introduction/Section-DroolsFusion.xml 2009-01-30 00:46:00 UTC (rev 25004)
+++ labs/jbossrules/trunk/drools-docs/drools-docs-fusion/src/main/docbook/en-US/Chapter-Introduction/Section-DroolsFusion.xml 2009-01-30 02:15:50 UTC (rev 25005)
@@ -1,11 +1,72 @@
<?xml version="1.0" encoding="UTF-8"?>
-<section version="5.0" xmlns="http://docbook.org/ns/docbook"
- xmlns:xlink="http://www.w3.org/1999/xlink"
- xmlns:xi="http://www.w3.org/2001/XInclude"
- xmlns:svg="http://www.w3.org/2000/svg"
- xmlns:m="http://www.w3.org/1998/Math/MathML"
- xmlns:html="http://www.w3.org/1999/xhtml"
- xmlns:db="http://docbook.org/ns/docbook" xml:base="../../">
- <title>Drools Fusion</title>
+<section version="5.0" xml:base="../../" xmlns="http://docbook.org/ns/docbook"
+ xmlns:xlink="http://www.w3.org/1999/xlink"
+ xmlns:xi="http://www.w3.org/2001/XInclude"
+ xmlns:svg="http://www.w3.org/2000/svg"
+ xmlns:m="http://www.w3.org/1998/Math/MathML"
+ xmlns:html="http://www.w3.org/1999/xhtml"
+ xmlns:db="http://docbook.org/ns/docbook">
+ <title>Drools Fusion</title>
+ <para>Event Processing use cases, in general, share several requirements and
+ goals with Business Rules use cases. These overlaps happen both on the
+ business side and on the technical side.</para>
+
+ <para>On the Business side:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Business rules are frequently defined based on the occurrence of
+ scenarios triggered by events. Examples could be: </para>
+
+ <itemizedlist>
+ <listitem>
+ <para>On an algorithmic trading application: take an action if the
+ security price increases X% compared to the day opening price, where
+ the price increases are usually denoted by events on a Stock Trade
+ application.</para>
+ </listitem>
+
+ <listitem>
+ <para>On a monitoring application: take an action if the temperature
+ on the server room increases X degrees in Y minutes, where sensor
+ readings are usually denoted by events.</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+
+ <listitem>
+ <para>Both business rules and event processing queries change frequently
+ and require immediate response for the business to adapt itself to new
+ market conditions, new regulations and new enterprise policies.</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>From a technical perspective:</para>
+
+ <itemizedlist>
+ <listitem>
+ <para>Both require seemless integration with the enterprise
+ infrastructure and applications, specially on autonomous governance,
+ including, but not limited to, lifecycle management, auditing, security,
+ etc.</para>
+ </listitem>
+
+ <listitem>
+ <para>Both have functional requirements like pattern matching and
+ non-functional requirements like response time and query/rule
+ explanation.</para>
+ </listitem>
+ </itemizedlist>
+
+ <para>Even sharing requirements and goals, historically, both fields were
+ born appart and although the industry evolved and one can find good products
+ on the market, they either focus on event processing or on business rules
+ management. That is due not only because of historical reasons but also
+ because, even overlapping in part, use cases do have some differences and
+ different requirements.</para>
+
+ <para></para>
+
+ <para></para>
</section>
More information about the jboss-svn-commits
mailing list