Once you have decided that leveraging the public cloud is right for your business there are many phases that need to happen to ensure that you remain compliant, in control and more importantly your IP (data) remains accessible and relevant. One area that needs to be top of your agenda is data integration.
The most cost effective cloud architecture is built upon public cloud services such as Rackspace and Microsoft. But that means your data now sits on cheap storage and multi tenanted server architectures.
When you move data to a public cloud, you need to appreciate the need for synchronisation with on-premise enterprise systems. Otherwise, users will duplicate data, save to USB and more worryingly have inaccurate data to manipulate. This typically is a stumbling point for cloud deployment and can hold up the project.
Like many architectural issues that need some face time when you move to the public cloud (such as security, governance, and performance), data integration requires upfront thinking and planning. Here's some of what you need to consider:
The amount of data to be placed in the public cloud
The type of data moving between architectures and the rate of change
The logging and auditing requirements
The exception-handling needs
Many enterprises don't like to think about data integration but if you do the upfront work, your public cloud deployment will work well.
No comments:
Post a Comment