Data Integration and App Integration

by Mike Y

            The Information Weekly article compares data integration and app integration. Application integration should be about the communication of even such as transactions or messages between applications while data integration should be about the flow of standardized data. Both are different and distinct and require different approaches when they are being implemented. The problem arises when vendors attempt to be vague about data standards guised as compatibility in order to appeal to a wider range of companies.

            This article is relevant to our class because how data is integrated indirectly affects data quality. If data integration is set up as an afterthought for data quality, then the data might be affected or vulnerable to attacks. I liked the article because it brought the subtle differences to my attention. I would have not have given it much thought at all. The data in Amazon’s database will obviously be a different format than Newegg’s, but also how the data is sent.

            Good planning should prevent many problems that would result from software incompatibilities. While being more secure, a properly planned and executed project should provide better and faster service for customers. They may not be able to notice immediately, but as the user base increases, problems of an ill planned project may become apparent as time goes on. That problem will be solved through a patch or update, but it can create even more problems further down the line.

Madsen, M. (2009, Marc 3). Key differences between data integration and app integration. Information Weekly, Retrieved from http://www.informationweek.com/news/software/bi/228900790

1 thought on “Data Integration and App Integration”

  1. I agree, I think companies should always keep data quality in mind because it is often overlooked. Ensure the data is consistent is hard when new data is coming in while old and outdated data still remain untouched.

Comments are closed.