[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [soa-rm] Interesting article on SOA and APIs
It is not clear to me what Patrick Gray thinks of as a service (his conceptual view of service). It is not clear that his view is consistent with the SOA RM.
In my view, the RM puts a lot of emphasis on the accessibility, and what Patrick is calling the API view is (in my opinion) more consistent with the SOA RM.
In fact, when doing services according to the RM and the RAF, you need to consider the universe of potential consumers and how to make your capability accessible
to that universe – and to lower any barriers to that accessibility. If your universe of potential consumers is very large, then it will look a lot like the API concept that Patrick mentions. If your universe is tightly constrained, it might be more like
the SOA version that Patrick mentions. Note also that Patrick mentions the use of ESBs. I’m thinking his conceptual view is of capabilities joined together via an ESB to accomplish some business
function – whether or not an external API is generated as a result. From: soa-rm@lists.oasis-open.org [mailto:soa-rm@lists.oasis-open.org]
On Behalf Of Mike Poulin My take is different. 1. Patrick
Gray (the author) points that it is IT is in the focus and that IT is creating the services, "I have long advocated viewing enterprise IT as a series of business
services that IT designs, builds, and maintains." I believe that this is the mistaken statement. In Business Services, IT has nober 2 role if any. A lot of Business Services exist with
no IT involvement. 2. "Until fairly recently, advocates of
this view would generally suggest IT implement Service-Oriented Architecture (SOA), a series of design principles that guided how an IT organization designed, built, and maintained applications. Rather than a focus on individual applications, SOA suggested
that multiple discrete applications and data sources be combined into services centered around a business process." First, IT is not only one who implements Service-Oriented
Architecture
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]