A Message Type architecture for SOA

One of the main goals of an SOA governance organization is to define processes and policies that can promote the development of reusable services. Thus, a service governance organization will participate in the entire service lifecycle, including identification, funding, design, deployment, operation, version management, and retirement.

A key issue of SOA governance is that it often turns a blind eye to data governance that can complement SOA governance. Even though the two goals are quite different, they share a set of metadata that is often referred to as the "Enterprise Data Model. EDM is the Logical Data Model of all information systems. If you want to, you can regard it as an ontology ). Its structure is often abstract and loosely coupled with the physical structure of the record system. However, all data elements stored in any known record system should come from an EDM element. EDM is often used to build a conversion ing between systems for data synchronization or replication.

In addition to EDM, data governance processes also affect service design, operation, version management, and consumption: these processes include data quality, metadata management, reference data changes, business rule changes, external data requirements, and data model changes.

The focus of this article is not the consistency between the data governance process and the SOA governance process. Instead, we will focus on the premise of effective collaboration between them: sharing and using enterprise data models.