The average corporate computing environment is comprised of hundreds to thousands of disparate and changing computer systems that have been built, purchased, and acquired.  The data from these various systems needs to be  integrated for reporting and analysis, shared for business transaction processing, and converted from one system format to another when old systems are

For a long time I’ve mulled over whether it’s necessary to keep both a batch and real time infrastructure for Data Integration.  After all, if you have a fully functional real time Data Integration solution, then why do you have to operate two sets of software and monitoring?  This is not to say that it is absolutely necessary

In recent discussions with Joseph Dossantos, he pointed out to me that the differences in architecting an MDM solution for Reporting, such as for a Data Warehouse, and for real-time transaction processing, go beyond the choice of batch versus real-time Data Integration.  Obviously, although the use of a batch ETL solution may be appropriate for integrating

I’ve been thinking a lot recently about Data Integration.  Since most applications at organizations are now purchased packages, it seems that most of the custom development an organization needs to do is around consolidating data into a Data Warehouse or integrating applications together.  Integration isn’t just one of a CIO’s biggest problems, it should be one