--- In [email protected], "Alexander Johannesen" <alexander.johanne...@...> wrote:
> so even if the pipe-dream of everything being > designed to work together from the get go is there, it is very far > from reality. But SOA doesn't make that assumption. Instead, it assumes that we *don't know* which components will need to interact in the future. Therefore, we must take steps to make it as easy as possible to assemble (dare I say integrate) components into a working whole on an ad-hoc basis. And do so repeatedly over time as needs and processes change. For example, today we might know that client A must interact with service X. We might also know that service X will be implemented as an aggregate of Y and Z. What we don't know is what other clients, in the future will need to connect with X? What other components will use Y and Z besides the components we know about today? SOA says that to more easily fulfill these future needs we should make define X, Y and Z such that they can easily integrated with other things in the future--by explicitly defining interfaces and makeing them discoverable. -Rob
