The Achilles Heel Of Cloud Computing – Data Integration

Loraine Lawson did a great job covering the topic of the integration challenges around the cloud and virtualization. She reports that “…a recent Internet Evolution column [by David Vellante] looks more broadly at the cloud integration question and concludes that insufficient integration is holding up both cloud computing and virtualization.”

In fact, what currently limits the number of cloud deployments is the lack of a clear understanding of data integration in the context of cloud computing. This is a rather easy problem to solve, but it’s often an afterthought.

The core issue is that cloud computing providers, other than Salesforce.com, don’t consider integration. Perhaps they are thinking, “If you use our cloud, then there is no reason to sync your data back to your enterprise. After all, we’re the final destination for your enterprise data, right?” Wrong.

Cloud computing is a great way to go in many instances, but if you think you don’t have to provide core data integration from the cloud computing platforms to the on-premise systems, you have another thing coming.

Indeed, there are many reasons to provide data integration within cloud computing problem domains. The first and foremost is that you need to maintain an up-to-date copy of your enterprise data on-premise in case of trouble that could come in the form of cloud computing outages, clouds going out of business, or clouds purchased by companies that have no interest in staying in that business. There are many examples of these occurrences now, and they will only get worse in the future.

However, the primary purpose of data integration within the context of cloud computing is to assist in driving processes between systems, on-premise and cloud-delivered, and to manage data integration across those very different and geographically dispersed platforms. Those who only had to deal with systems talking intra-data center have some new challenges when they consider cloud computing.

These are the problem domains that require, dare I say it, data integration architecture and strategic technology. This means that you need to consider all of the source and target schemas, and how you’re going to securely and reliably move data between those points, accounting for the differences on the fly. Moreover, you need to consider MDM issues, as mentioned above, as well, as security, and data governance.

Here are a few words of advice:

First, consider the overall requirements of the business. Sounds obvious, but many who deploy cloud computing systems do not have a complete understanding of the overall business requirements.

Second, focus on the holistic architecture, on-premise and cloud-delivered, including how they will and should exchange data to support the core business.

Finally, select the right data integration technology for the job, and do so only after taking everything into account. You’ll find that there are both on-premise and on-demand options, and in many instances you may have to mix and match solutions.

You can’t do the cloud without data integration, and until we get data integration right, you can’t do the cloud. Pretty simple, if you think about it.

This entry was posted in Cloud Computing, Customers, Data Integration, Data Warehousing, Master Data Management and tagged , , , , , , . Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>