I agree with you on that SOA is about managing interactions between systems, but I think Gervas's point is the improper SOA creates a bigger dish of spaghetti because some developers just think creating bunch of web services between systems and implementing some web service monitoring tool is enough to integrate application silos. Improper attempt to integrate systems creates a bigger dish because users, who were reluctant to integrate before, are now beginning to do so because they think it can be easily done.
Finally, I also agree with you on the bigger the need to integrate systems, the bigger the need for a SOA. Cheers, H.Ozawa Robin wrote: > Oh no, here we go again with the "Spaghetti" qualifier! > Spaghetti was used in the past to depict application integration > before EAI (and SOA). > > I think SOA is about managing the Spaghetti and not removing the > Spaghetti. > > The biggest the Spaghetti, the bigger the need for a SOA. > > I just hope people will not equate SOA = Spaghetti-Oriented > Architecture now. > Robin > > --- In [email protected] > <mailto:service-orientated-architecture%40yahoogroups.com>, "Gervas > Douglas" <[EMAIL PROTECTED]> wrote: > > > > These statistics vary wildly, and lead one to conclude that SOA must > > be in the eye of the beholder, because one company's "SOA" may be, in > > someone else's view, a Spaghetti-Oriented Architecture or "JBOWS" > > (Just a bunch of Web services). > > > > Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
