Sanjay Patil

Last month we described the enterprise integration environment, as well as the integration problem domain and entailing architectural requirements. This month, we'll look at how Web services address these architectural requirements, and provide a sidebar that examines the key differences between Web services and various component technologies. Solution: Web Services Web services are based on several (emerging and de facto) standard technologies - primarily SOAP, WSDL, and UDDI. SOAP is an XML-based packaging protocol and is neutral with respect to the network access protocols or component models of: The interaction patterns the endpoint supports The abstract models for the data structure supported by the endpoints The concrete bindings of the abstract data models (which are needed to exchange data formats on the wire) The concrete bindings of endpoint services to tra... (more)

Integration Approaches: Web Services vs Distributed Component Models

This article, the first of two parts, will compare and contrast Web services with other distributed computing component technologies such as CORBA, J2EE, and DCOM. We look at these approaches in the context of their respective capabilities in support of integration solutions and application architecture domains (e.g., loosely coupled versus tightly coupled applications). These technologies are complementary, but the most important consideration for choosing a particular technology is its suitability for a particular problem/solution domain. At a high level, an enterprise applicat... (more)