Thus, when we decompose business model following "business wants tight business coupling at the top", we end up with relatively tight coupled business autonomous services. I said 'relatively' because there may be a degree of decoupling but business reuse based on this decoupling is not that gigantic as early-day SOA promised, correct?
>From the business perspective, do we really have sustaining case of business reuse? Should we talk about reuse rather than about composability and composition participation for business services? - Michael ________________________________ From: "[email protected]" <[email protected]> To: [email protected] Sent: Tuesday, May 5, 2009 7:58:30 AM Subject: [service-orientated-architecture] Re: Narayanan on buillding reusable services We consider coupling from several dimensions - Business - organization - information - process - implementation - device the 'tightness' of coupling in one area may offset the amount of 'looseness' in another. And we should always consider that whilst loose technical coupling in the lower layers of that 'stack' may be desirable, there are often good reasons why the business wants tight business coupling at the top. Lawrence --- In service-orientated- architecture@ yahoogroups. com, Michael Poulin <m3pou...@.. .> wrote: > > How good 'loose' coupling' is for the business? > - for the business interface? > - for the business service? >
