We use cookies and other similar technologies (Cookies) to enhance your experience and to provide you with relevant content and ads. By using our website, you are agreeing to the use of Cookies. You can change your settings at any time. Cookie Policy.
Start a Discussion
Event Processing

Should SOA and Event Processing Be Joined at the Hip?

Vote 0 Votes
Reading over Jason Bloomberg of Zapthink's recent blog, he details the growing importance of Business Event Processing to SOA, saying: The bottom line, however, is the business story. BEP, combined with SOA, further bridges the gap between business and IT.  So do you think SOA and event processing should be joined at the hip?

10 Replies

| Add a Reply
  • It would be interesting to know why not...

  • Haven't we been here before? SOA and Event Processing are peers and complements. See my 2006 Event-Driven Architecture overview.

  • I agree with Brenda. I wrote on the topic almost 5 years ago in 2005

    Modi, Tarak - Event-Driven Architecture: Achieving Architectural Agility (Web-Services Pipeline) June 10, 2005

    Are we going around in circles thinking that we're making progress while all we are really doing is chasing our own tails?

  • I will say Event Processing with BPM and SOA bridges the gap between business and IT. If you want to have a successful Event processing implementation, you should have started your BPM right, until enterprises understand their process you can't your Events processing right.

  • More than joined at the hip... They should be genetically fused as a single organism! In a hyper-competitive business climate, situational awareness is everything, and decision makers need those real-time dashboards! This is what SOA was designed for.

  • Presumably the author forgot to mention that "BEP" is a vendor marketing team's attempt to rename the technology space known as "CEP", and that from an SOA viewpoint, event processing is synonymous with "asynchronous services" (on events/messages).


  • Brenda is spot on. Peers and complements, as she wrote in 2006.

    - Mark Palmer CEO, StreamBase

  • As already mentioned by others SOA and Event Driven Architecture (EDA) are complementing architectures. The term SOA 2.0 coined few years ago describes the unifies architecture of Services, Events and Processes.
    A Responsive Organization needs Services Agility as well as Business events handling

  • SOA is about Architecture, in the last five years or so the focus has been on Architecture with "invokable", standards based, services. EDA is also about Architecture. The EDA focus is "subscribable" services (or as I've said in the past "the service is a topic is a service"). Services oriented Architecture as an approach to Software development is at least 45 years old (just not done today exactly the way we did it back then). EDA is a bit younger, but they are both part of the natural evolution of Software Architecture with an orientation toward the exploitation of services.

    Remember, events happen, we can't stop that, we now have more formalized (and in many cases COTS Middleware assisted) ways to deal with them efficiently along with the compute power needed to do things like BEP/CEP (analytics?) that we couldn't have done even a few years ago without seriously high powered computers.

  • One of the main SOA principles ‘Loose Coupling’ is possible with recommended use of Event Driven Architecture. Of course, BEP modeling enables loose coupling and if care is not taken it can get to extreme loose-couple (Good luck with troubleshooting!)

Add a Reply

Recently Commented On

Monthly Archives