You are here:  Home  >  Data Blogs | Information From Enterprise Leaders  >  Current Article

Data Interchange Models: What are They?

By   /  June 16, 2017  /  No Comments

Click to learn more about author Michael Blaha.

Let’s continue last month’s discussion about different kinds of data models and look at data interchange models. My interest in this topic was piqued by several encounters with overly complex data interchange models.

Data Interchange Model

A data interchange model provides the means to convey data among applications. Here is the basic motivation. A pairwise coupling of applications leads to n*(n-1) data interfaces.

data interchange model

In contrast, coupling of application via an intermediate representation leads to 2*n interfaces. A data interchange model is the intermediate representation.

data interchange model

An interchange model can be used as a specification for data transfer or it can specify the schema of an interchange database. The source applications must translate their data into the data interchange format. Similarly, target applications must use the data interchange format to populate their own internal data structures. Thus, a data interchange model mediates applications and stands apart from them.

An interchange model is not intended for building an application. An interchange model should have a small schema and be straightforward to parse. It need not be concerned with enforcing data quality. The sole purpose of an interchange model is to provide a means for translating from source to target.

Given the need for small schema size and flexibility, a typical interchange model combines metadata and data. This can make them tricky to define and understand.

Data Interchange Model vs. Application Data Model

A data interchange model is much different than an application data model. Interchange data is transient. In contrast, application data is persistent and provides the memory for an application.

Furthermore, interchange data models should normally be abstract and small in size. Their purpose is to move data. In contrast, application data models tend to be tangible and directly represent business data. Application data models are often large (often hundreds of tables or more) as they try to finely describe data to enhance data quality.

In Conclusion

Skilled developers recognize the importance of data models. Data models let you specify data and databases as well as the applications that work with data.

The precise content and approach to a data model depends on its purpose. There are many kinds of data models, including application model, data warehouse models, enterprise models, and interchange models. This blog called attention to interchange data models and contrasted them with application data models.

About the author

Michael Blaha is a consultant and trainer who specializes in conceiving, architecting, modeling, designing and tuning databases. He has worked with dozens of organizations around the world. Blaha has authored seven U.S. patents, seven books many articles, and two video courses. His most recent publication is the Agile Data Warehouse Design video course from Infinite Skills. He received his doctorate from Washington University in St. Louis, and is an alumnus of GE Global Research in Schenectady, New York. You can find more information with his LinkedIn profile or at superdataguy.com.

You might also like...

Data Literacy and the Colin Powell Rule: From Frontline Field Support to Back Office Operations

Read More →