YOUnite Data Store vs Federated Data Stores

In Master Data Management data can be stored in a variety of ways but generally falls into one of two categories, often a hybrid of these two: YOUnite Data Store or Federated.

YOUnite Data Store

The YOUnite Data Store data management refers to a model where domain data records are stored in the MDM Data Hub, which serves as a database as well as a router that receives and accurately transmits the data to be shared to the proper systems that have subscribed to data changes. In other words the Data Hub provides the master data to which all applications subscribe. In the case of YOUnite, the domain data records would be stored in YOUnite's Data Hub/data store. A YOUnite Data Store data management model is often used when the entire organization is comfortable or mandated to migrate a domain to a single store. The YOUnite data store is optimal for reference data such as a list of infrequently-changed data, such as states, countries, zip-codes, etc. 

Federated

Federated data management refers to a model where domain data records are stored locally with their source application database instead of in the MDM Data Hub. The source applications "subscribe" to receive data updates from other applications they consider to store the "record of truth." The hub routes the data based on publication and subscription settings configured by each application and ensures data quality. Federated domains require adaptors, metadata, and governance configurations and allow organizations to maintain a high level of control over their data. See Adaptors and Federated MDR for more information on mapping federated domains to the MDM Data Hub. 

Coexistance MDM Model

The power of a federated system allows for the "Coexistance" MDM model.

A Coexistence style allows for maintaining a master data record in the same way as the YOUnite Data Store, but your master data is stored in a system connected to YOUnite via an adaptor and is recognized as a source of golden store for all or a subset of systems in the ecosystem. 

The standard YOUnite governance resources are used to control the flow of master data out of the golden store.

As expected it is incumbent for the data stewards to insure that all of the properties of the data domain model is normalized for all subscribing systems and that the master data is clean before publishing out to the ecosystem.

Data Domain Model Schemas

A domain Model Schema refers to the attributes (properties), format, and other metadata that defines how a specific domain should expect to store the data (either in the YOUnite Data Store or Federated), for the purposes of standardizing how data is exchanged between systems. The Data Governance Steward is responsible for configuring and maintaining domain model schemas. A  domain model schema is a JSON object describing/defining the properties for the domain's schema. The root node of the model schema is the properties element. See Valid Property Names and Valid Types for ModelSchema Properties below.

Similar concepts and often used to describe a data domain include:

• Model or data model
• Data dictionary
• Schema