There have been some questions as to whether data integration by design actually represents a data integration solution. Data integration by design actually represents multiple data integration solutions and goes beyond what prior art data integration methods provide. (Please click "Read More" for the rest of this post) ---->
Most importantly, data integration by design forms integrated databases that are the foundation for integrated data architectures. The integrated databases directly interact to function in harmony supporting tactical and strategic business requirements of the organization. On the other hand, disparate databases form the foundation for disparate data architectures which is the root cause of the data integration problem. Each disparate database is characterized as an island of disparate data that does not directly interact with any of the other disparate databases. Simply stated, disparate databases work alone while integrated databases work together.
Data integration by design is the first database design methodology that defines data access paths between databases using newly defined commonality constraints. Via these data access paths, database tables from a first database may be reliably joined to database tables from a second database to from consistent and coherent return data sets.
Prior art data virtualization was based upon unintentional data set commonality between two or more databases to join in producing return data sets. There is no referential integrity in unintentional data set commonality so the return data sets are not easily verifiable and are often not reliable.
Integrated databases combined with data federation methods provide a virtualized verifiable and reliable type of data integration. Integrated databases, with their defined data access paths and referential integrity, add the data integrity that was missing in prior art data federation.
Finally, data integration by design also supports the development of data warehouses. The main difference is that these data warehouses use integrated databases as their data sources. As such the resulting data warehouse is not dependent upon data transformations and the data warehouse remains integrated with these source databases. The integrated data architecture support roll-ups and drill downs between source databases and their associated data warehouses. In addition, these integrated data warehouses are also integrated with any other integrated databases such as master data management databases, other transactional databases, and other integrated data warehouses.
There should be no doubt that the integrated data architecture is far, far superior to the disparate data architecture in agility, efficiency, and effectively! Please request the Data Integration by Design whitepaper for details.