No, Kamen. I explained it in my yesterday post. - Michael
----- Original Message ---- From: kaburov <[EMAIL PROTECTED]> To: [email protected] Sent: Monday, June 30, 2008 9:41:12 AM Subject: [service-orientated-architecture] Re: Legacy into SOA (was Vandersluis on a Data Abstraction Layer's Benefits) Well at the moment I do not have time to read and analyze all messages about SOA and integration But there are similar scenarios in other areas too: mechanical engineering, building, textiles. There are parts that are not designed to work together and sometimes they have to be made/fixed/integrat ed to work together. In such cases there are 2 main options: to make changes so that they somehow work together or to build from scratch one or more parts with proper design. With different words it is possible and may be easier to build car and house from old parts (scrap) but the majority of people prefer new car/house because is better and simpler to use and support Also it is possible to make dress from patches but majority of people prefer new dress I think it is similar case with software. SOA can take the role of new car/house/dress Michael is this what you mean when you write 'SOA and integration are not the same things, and even more - they are opposite things'? Kamen --- In service-orientated- architecture@ yahoogroups. com, Michael Poulin <[EMAIL PROTECTED] .> wrote: > > In this forum, I believe we agreed that SOA and integration are not the same things, and even more - they are opposit things > > - Michael > > > ----- Original Message ---- > From: kaburov <[EMAIL PROTECTED] > > To: service-orientated- architecture@ yahoogroups. com > Sent: Sunday, June 29, 2008 8:34:23 AM > Subject: [service-orientated -architecture] Re: Legacy into SOA (was Vandersluis on a Data Abstraction Layer's Benefits) > > > Michael IMHO integrating parts that are not designed to work together > is common problem in many companies. One engineering best practice is > that simplest solution is the most reliable solution so such > companies take the road to simplification and consolidation of their > software systems. They can share this investment with other companies > that have similar style, probably subsidiaries, branches, etc >
