Switch: key issues of data integration

Microsoft architect Journal No. 8th, A flexible model for data integration By Tim Ewald and Kimberly Wolk we always tried to consider communication protocols and messaging methods in the past, but for integration, a flexible data model is the most critical. There are running challenges in systems integration for developers TS and developers, and the industry has focused on XML, Web Services, and SOA for solving integration problems by concentrating on communication protocols, participating in regard to adding advanced features that support message flow in complex network topologies. however, this concentration on communication protocols has taken the focus away from the problem of integrating data. flexible models for combining data into ssdisparate systems are essential for successful integration. these models are expressed in XML Schema (XSD) in Web service-based systems, and instances of the model are represented as XML transmitted in soap messages. in our work on the architecture of the msdn technet publishing system (MTPS) We addressed three pitfalls. we'll look at what those pitfalls are and our solutions to them in the context of a more general problem, that of integrating customer information.