There is a subtile difference. If we talk about integration, we usually assume there are more than 2 servers/applications. On the otherhand, when we talk about architecture, it is possible to start with just one application with condition that we take other servers/applications into account.
As was pointed out last week, most projects tend to focus on a single application because development/maintenance still tend to be vertical. It's better to start horizontally across applications, but if the person who I'm talking to just head an application team, that's not possible. IMHO, saying that SOA is about integration, actually limits SOA. I prefer to say that SOA is about architecture which makes integration easier when need of integration can be justified (usually later in the project). :-) H.Ozawa --- In [email protected], "Rob Eamon" <rea...@...> wrote: > > Anne wrote: "Maybe I'm just being pedantic, but I think it's important > to distinguish between integration and architectural activities." > > Are these two activities necessarily different? > > -Rob >
