Last week, Joe wrote about the impeding event-driven architecture (EDA) wave.  EDA, as anyone within earshot of my soapbox knows, is a natural complement to SOA.  While I normally blog about “event processing” related topics at elemental links, I just read a good paper from Coral8’s Mark Tsimelzon that will resonate with ebizQ readers. 

The paper describes 10 basic Complex Event Processing (CEP) patterns that appear repeatedly in CEP applications.  The patterns are of the style of Gregor Hohpe and Bobby Woolf’s excellent Enterprise Integration Design Patterns.  In addition to style similarities, you can see many of the message based enterprise integration patterns (channels, enrichment, filtering, routing) present in the CEP patterns.

The 10 CEP patterns Mark presents are:

If you are curious about CEP, take a look at Mark’s (easy to read) paper.

[Disclosure: Coral8 is NOT a client of Elemental Links, Inc.]

Posted by brendamichelson in EDA | Permalink | Comments (0) | TrackBacks (0)

Updated 8.23.2006 at 11:04 to insert "DRAFT" into the post title, and add the following clarifying note:

The linked document is a "work in progress", and not (yet) an official RFI.  In other words, please review the RFI for content (additions, changes, deletions), not for submitting a response.  Thanks.

[The original post starts here]

For readers of elemental links, this is a duplicate post. I'm going for max reach!

The Object Management Group’s SOA SIG is looking for community (practitioner, vendor, researcher, observer) feedback on a draft request for information (RFI) on event-driven architecture (EDA) and its relationship with service-oriented architecture (SOA) & business-process management (BPM).

Here’s the RFI Summary:

The EDA Sub-group of the OMG SOA SIG seeks information from members of the EDA, BPM and SOA community as well as anyone interested in promoting standards in this area. Requested information will be evaluated by the EDA Sub-group, resulting in the development of Requests for Proposal(s) (RFP) for standardization of Event definition, relationship between EDA, BPM and SOA that will ultimately allow development of standards for Complete Life Cycle of Events -Ontology of Events, Sense and Respond Services, Events Metrics and processing of complex events. Please note that it is our intent to develop modeling standards for the EDA/SOA and EDA-Business Process interaction and provide standards for the implementation of that interaction as well.

For those (like me) not completely familiar with the OMG process, here’s the description of the RFI process taken from section 8 of The OMG Hitchhiker’s Guide, V7.3:

The intent of the Request for Information (RFI) is to gather information for the purpose of guiding a subgroup in its efforts to provide solutions to industry problems. The RFI is an optional process used by a subgroup to canvass a targeted industry segment for one or more of the following purposes:

• Acquiring general or specific information about industry requirements.
• Soliciting assistance in identifying potential technology sources.
• Soliciting input to and validate a subgroup’s roadmap.

Generally speaking, the RFI process determines which Request For Proposals (RFPs) get issued (and, based on negative feedback, which don't) or influences the way a particular RFP is constructed.

There are no restrictions on who may receive or respond to a RFI. Both OMG Members and non-members can respond. RFI Responses may include information about relevant technologies, products, standards, research, requirements, and other guidance for the subgroup.

If you are interested in EDA (simple, stream, complex), take a look at the RFI and provide comments to Dr. Harsh Sharma. The plan calls for a final review of the RFI at the OMG’s September Technical Meeting in Anaheim.

I suppose this is where I say “I’m going to Disneyland!” I am a guest contributor (no $ exchanged either way) to the EDA subgroup of the OMG SOA SIG.

Posted by brendamichelson in EDA • SOA • architecture strategies | Permalink | Comments (0) | TrackBacks (0)

If you read my elemental links blog, you can skip this post.  If you don't, and you're interested in event-driven architecture, there are three new EDA related posts over there this week.  [A personal blogging best.]

Tuesday, I shared some illustrations and discussion from my "EDA and SOA: Complements and Peers" talk at the OMG SOA SIG meeting.  Wednesday, I featured a conversation with Bob Covington, CTO of Rhysome.  Today, I'm talking about StreamBase's Da Vinci Coder contest.

Posted by brendamichelson in EDA • elemental links | Permalink | Comments (0) | TrackBacks (0)

Ugh!  That was my reaction when I first read about "SOA 2.0".  As Mark Little wrote "Giving an architectural approach a version number is crazy: it makes no sense at all!"

And please, do we need any more confusion on the relationship between SOA and EDA?  I think not.  And I'm not alone.  Neil Dutton-Ward at Macehiter Ward-Dutton has created an online petition to "Stop the Madness".  The petition reads as follows:

We've created this online petition because we're dumbfounded at the attempt by certain parts of the IT industry to create and give weight to the term "SOA 2.0".

We and others have blogged about this already: Joe McKendrick, Mark Little, and Duane Nickull to name but three.

As Duane said recently: "Normally, when someone comes out with a new buzzword that doesn't really have any substance, most people merely complain quietly and go about their business."

We would dearly love, just this once, for things to be different. Industry does not, at this point, need more confusion around SOA. SOA has real value, but industry at large is only just coming to terms with what it means and what it can do. Inventing terms like "SOA 2.0" might help some analysts and vendors make money, but overall, in the long run it damages us all.

In part, this petition is an experiment. Many people have discussed the power of the Web to aggregate and demonstrate the power of individuals: but it would be good to see if, through this simple web page, we could pressure the protagonists into backtracking on SOA 2.0.

I encourage practitioners who are sick of the hype, and looking for  real information/ammunition to introduce/extend SOA in your business to click through this link, and sign the petition.  (Just don't double submit as I mistakenly did).

Posted by brendamichelson in EDA • SOA • architecture strategies | Permalink | Comments (0) | TrackBacks (0)