The past three articles have looked at how different systems can be integrated. Specifically they focused on two core technologies: service-oriented architecture (SOA) and event-driven architecture (EDA), and two SOA implementations: Simple Object Access Protocol (SOAP) and REpresentational State Transfer (REST).

Now that we have a plan for how we might integrate the different systems in our enterprise, the next step is to measure the impact of additional load generated by new consumers of our services and how we might mitigate that load. This article begins by looking at the challenges in understanding the data in each system and the need for “one data model to rule them all?. It then reviews the Canonical Data Model enterprise integration pattern as a solution to the data model problem and the construction of a Canonical Data Store as a solution to manage load on existing systems. Finally, it reviews the challenges in managing a Canonical Data Store individually as well as the complete SOA, EDA, and Canonical Data Store deployment.

Read the full article in about:virtualization