BACKGROUND IMAGE: iSTOCK/GETTY IMAGES
Cloud compatibility concerns bust hopes of widespread cloud bursting
There was a time where cloud bursting was the hot topic on every IT administrator's mind. In the era of pay-as-you-need-it cloud services, the idea to go to the public cloud only when extra compute capacity is needed has natural appeal.
The reality of cloud bursting is more complex, however, and cloud compatibility is a barrier for many businesses. For cloud bursting, the private and public clouds need to communicate fluidly with one another, but that often is not the case.
This handbook examines the practicality of cloud bursting and where it might be better in theory than in practice. Cloud expert David Linthicum writes that it's important to keep in mind a potential lack of feature compatibility. For example,what Amazon Web Services offers in its public cloud is more advanced in most cases than what's found in private cloud technologies, so bursting an app to AWS brings complications that can't go overlooked.
Linthicum lists three realities that admins need to consider: private clouds are not cost-effective, cloud compatibility is virtually non-existent and messing with the deployment model will make everything complex and expensive.
Cloud consultant Jim O'Reilly writes about four ways to make cloud bursting work for your business. The No. 1 item is to forget the private or hybrid cloud and put everything in a public cloud. Another way to maintain cloud compatibility is to roll everything in-house and have internal cloud bursting.
Finally, cloud consultant Dan Sullivan looks at the challenges that cloud bursting presents and implores businesses to consider all angles before making any commitments. Latency can be an issue for apps that move from private to public cloud, writes Sullivan, and admins need to know if data copies will be available in both clouds.