SOA is about loosely coupled systems, message based communication and business process orchestration - Statement taken from MicrosoftWay camp
Would like a summary quotation from JavaPlatform and EnterpriseServiceBus vendors besides BigBlue. --DavidLiu request
See ServiceOrientedArchitecture for now.
A worthwhile undertaking due to prevalence of SOA related matters impacting all IT application areas
Current ServiceOrientedArchitecture and related pages are too congested. -- dl
I do not have energy to tackle this single handedly. But I suggest these aspects to start:
Resources
successful web services http://workingknowledge.hbs.edu/item.jhtml?id=4800&t=technology
MS Jan04 SOA basics http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmaj/html/aj1soa.asp
Computerworld myths of Web Services http://www.computerworld.com/printthis/2004/0,4814,95053,00.html
SOA missing pieces http://cio.co.nz/cio.nsf/0/D368C5F360A61F65CC256F0D007E70AD?OpenDocument
WindowsCommunicationFoundation and SoaIsPeace tenets by DonBox http://msdn.microsoft.com/msdnmag/issues/04/01/Indigo/default.aspx
SoaIsPeace. Iff JavaAndDotNet work together then there will be less WebServicesInteroperabilityConcerns
Most critical technological problem identified in late 2005 lies with the domain of SoaSystemsManagement.
BigBlue and MicroSoft both participates at WebServicesInteroperabilityOrganization where there have been significant progress in areas like WebServicesSecurity. However at the product level even the venerable WebServicesDescriptionLanguage level interoperability between vendors is said to be broken (note WS-I Basic Profile was adopted two years ago in mid 03 that aimed to resolve ambiguities in the WSDL). -- Source: industry report on JavaOne meeting in mid 2005.
One WikiReader of SOA material at C2 speculates in late 2005