RE: [soa-rm-ra] Updated Section 4.3

["Poulin, Michael" <Michael.Poulin@uk.fid-intl.com>]

In Fidelity, we just finished our SOA Blueprint review and, with regard to SOA - EDA relationship, stated that SOA Service may have EDA specific public interface. That is, the interface described in the Service Description and published in the Service Registry/Repository.

 

We outlined the same two communication patterns - notification and conversation, mentioned reliable messaging as a special form of EDA, and omitted all other details.

 

Thanks,

- Michael

Important: Fidelity Investments International (Reg. No.1448245), Fidelity Investment Services Limited (Reg. No. 2016555), Fidelity Pensions Management (Reg. No. 2015142) and Financial Administration Services Limited (Reg. No. 1629709, a Fidelity Group company) are all registered in England and Wales, are authorised and regulated in the UK by the Financial Services Authority and have their registered offices at Oakhill House, 130 Tonbridge Road, Hildenborough, Tonbridge, Kent TN11 9DZ. Tel 01732 361144. Fidelity only gives information on products and does not give investment advice to private clients based on individual circumstances. Any comments or statements made are not necessarily those of Fidelity. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you received this in error, please contact the sender and delete the material from any computer. All e-mails sent from or to Fidelity may be subject to our monitoring procedures. Direct link to Fidelity’s website - http://www.fidelity-international.com/world/index.html

---

From: Jeffrey A. Estefan [mailto:jeffrey.a.estefan@jpl.nasa.gov]
Sent: 10 December 2007 19:33
To: soa-rm-ra@lists.oasis-open.org
Subject: Re: [soa-rm-ra] Updated Section 4.3

Dave,

 

I am trying to avoid the whole IP addressing issue here.  Really not interested for this Reference Architecture for SOA.  Obviously, there are numerous IP addressing schemes that include unicast, broadcast, multicast, anycast and their supporting underlying protocols.

 

What we MUST do, is address the apples/oranges issue I mentioned in my prior e-mail regarding the two different modes of message exchange (joint action and event notification) and the two most common MEPs associated with those modes in support of SOA-based systems.   I'm also not interested in delving into the whole Event Driven Architecture (EDA) space including complex event processing (CEP), though we should touch ever so slightly on the relationship between EDA and SOA as architectural paradigms.  I had some words to that effect but they were rejected by the review board and removed.

 

Bye for now...

 

 - Jeff E.