June 2, 2011
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 of their biggest focuses (maybe following only security, business continuity, and core application support).
Today, I was thinking about Data Integration in Cloud Computing, and I realized that Data Integration is the key enabler to Private Cloud / Public Cloud hybrid computing. In fact, Data Integration is key to any interaction between data stored offsite (“In the Cloud!”) and onsite.
May 8, 2011
Have you heard about this phenomena that your mind fills in pieces of a scene it expects even if your eyes don’t see something?
I’ve been reading various books on Data Integration lately because I am thinking of proposing my own book on the subject and I was interested in what was already written. So I was reading a chapter in “Data Integration Blueprint and Modeling” by Anthony David Giodana on various Data Integration architectures and he described a “Federated” architecture as being one where tables in various databases on even seperate servers are joined together. Now this is a perfectly acceptable achitectural concept but is, in my experience, so incredibly slow that it is not really a viable option. ( I should mention that Mr. Giodana does say that it is not suggested for real-time processing. ) I had basically removed the option from my mind until I read his description. There may very well be times when you don’t want all the duplicate data involved in replication but since it was not something I ever intended on doing, it was gone … gone from my brain.
May 2, 2011
At Enterprise Data World I gave a workshop which was an introduction to Data Integration. The material seemed to fall into two types: information about technologies and information about … architecture? patterns? design? methodology? For example, a Hub and Spoke architecture is not a technology but a way to design interfaces in an efficient way. For now, I’ll call it architecture or design.