+1. Many people with EAI background tend to context map between 
application domains.
While people with a SOA background tends to define service domains based 
on cross-cutting
concerns across application domains.

I think many people hold reservation about integration bus because there 
are often used as
a tool to connect between application domains. I view them as a 
framework to implement a model
in a service domain.

H.Ozawa

jeffrschneider wrote:
> Most large companies that I visit have some variation of 
> an "Integration competency center". This is a group that specializes 
> in "integrating" systems. It is now common for this group and the "SOA" 
> team to either be one and the same, or they work together closely. An 
> item that has recently caught my attention is the different units which 
> these two groups work with. Many people with an integration background 
> tend to "integrate" silo-oriented applications. While people with a SOA 
> background think about "disintegrating" (or breaking into parts) 
> and "re-integrating" (according to a service boundary). 
>
> I feel like our industry has done a good job of showing people how to 
> integrate systems and a poor job of teaching people how to disintegrate 
> them. Am I alone?
> Jeff
>
>
>
>
>
>
>
>   

Reply via email to