Re: [soa-rm-ra] Make way for SOA 2.0

[Ken Laskey <klaskey@mitre.org>]

Jeff,

It appears the EDA model just identifies multiple service consumers and
providers.  Does the following make sense (assuming the extreme
where every interaction is through a service)?

- The entity which identifies the triggering event is a service consumer
(SC1) and the service it consumes is the one providing the appropriate
response.  Responding to an event instance is automated and SC1 may
or may not be informed of any particular event instance.  In setting
up the automated response, SC1 may, for example, make use of a pub/sub
service.
- The triggering event accesses a service to make itself known, thus the
mechanism that does the event post is also a service consumer of the
post-acceptance service.
- The post-acceptance service initiates an interaction consistent with
the response wanted by SC1 (either customized to SC1 or SC1 decided the
set offering was acceptable) and so is also a service consumer.

The targets of all these consumers are event processor capabilities
accessed through their corresponding services.

If my description doesn't warp things too much, EDA is more about
establishing and executing automated workflow than it is about an
alternate architecture.  I see EDA as providing requirements for an
RA and an eventual concrete architecture.

Ken 

At 01:50 PM 5/18/2006, Jeffrey A Estefan wrote:
> Hello Ken!
>  
> I don't think we'll want to get too wrapped around the
> SOA/EDA axle in our RA work.  As Joe points out, the discussion is
> not new.  The fact is, both are viable architectural styles that are
> more synergistic than orthogonal.  In SOA, the principal actors are
> service providers and service consumers; in EDA, the principal actors are
> event posters and event processors.  
>  
> The industry is still struggling with SOA adoption (and
> hopefully, we [OASIS] can help!).  EDA requires expertise in CEP
> (Complex Event Processing).  As a consequence, EDA is a bit ahead of
> its time and will likely take more time for industry adoption. 
> You'll often hear about it in the context of the "real-time
> enterprise."
>  
> Bye for now...
>  
>  - Jeff
>  
>

--
     ---------------------------------------------------------------------------------
  /   Ken Laskey                                                                \
 |    MITRE Corporation, M/S H305    phone:  703-983-7934   |
 |    7515 Colshire Drive                    fax:      703-983-1379   |
  \   McLean VA 22102-7508                                              /
    ----------------------------------------------------------------------------------