Web Services Interoperability Concerns

WebServicesInteroperabilityConcerns deal with a range of issues that need to be resolved for the realization of promises of WebServices.

As at early 2005, the foremost consideration is security related, including IdentityManagement schemes and privacy issues.


IdentityManagement

There are three forces at work.


WebServices wars

Microsoft said SoaIsPeace, peace the MicrosoftWay as they said (see MicrosoftIndigo) EnterpriseServiceBus based SOA is proprietary, and therefore have vendor lock-in concerns.

Their opposition is laying similar charges at Microsoft.

See also Top Ten ESB myths at http://www.ftponline.com/reports/vslivesf/2005/vanhuizen/


Common standards do not ensure interoperability

An example being XmlSchema which is supposed to enable loosely coupled services to interact. However it is said to have numerous bugs, ambiguities, and incompletely implemented features that have not helped with heterogeneous environment service integration. (ref point 7 of article at http://www.builderau.com.au/architect/webservices/0,39024590,39193448,00.htm)


Resources

News and current events

Older material

See also WebServicesSecurity


CategoryWebServices CategorySecurity CategoryEnterpriseComputingConcerns


EditText of this page (last edited March 8, 2006) or FindPage with title or text search