OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

soa-rm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [soa-rm] FYI: BEA SOA Reference Diagram


+1
In practice, as you say, it is difficult to imagine an implementation that
gets away with just oner "service" particularly if you define (as some have
proposed, and which I would propose that we accept) *any* call to *any* type
of resource (a data lookup, for example) also as a service, but this does
not make it an underlying rule of the RM that multiple services are required
for "it" to qualify as an RM-compliant SOA...

-Peter

Questions:
1. Is it necessary that there be more than one service in order that SOA be
SOA? 
2. If yes to #1, is it necessary to call services only in sequence?

My gut feeling is that having multiple services is probably a given for any
specific implementation of SOA, however it is not a requirements for
something to be service oriented.  If I architect one application and build
it with a single service, service description, policy set, (+
whateverElseGetsInTheReferenceModel), is that service oriented architecture?
I think yes.




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]