Re: [service-orientated-architecture] Re: SOA Book & Discussio

[Ashley at Metamaxim]

Mike wrote:   > It's true that the issue with the banking service here is not purely > about modelling, it's one of dependencies. But the dependency is not > on the *provider*, it's on the account *data*, that is the shared > state.   I would describe it as a dependency between the customer and the provider, where the latter I take to include the assets in the provider's possession or keeping.   I agree it is data in this case. But if the service being considered is a safety deposit box, the assets would be physical. I was trying to be abstract enough to cover both (probably foolish).   > I would quite happily use an "international transfer" > service/operation from provider X if that provider could safely > deposit the money in my account managed by provider Y.   OK. But I would say that if you do this, and leave the account with Bank X open (i.e., do not close it), there are now two services instances in existance.   Rgds Ashley __._,_.___ SPONSORED LINKS Computer software Computer aided design software Computer job Soa Service-oriented architecture YAHOO! GROUPS LINKS  Visit your group "service-orientated-architecture" on the web.    To unsubscribe from this group, send an email to:  [EMAIL PROTECTED]    Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. __,_._,___