Who wouldn’t want to maximize control and minimize costs by running a few servers in-house and borrowing public cloud resources when the odd demand spike occurs? This arrangement is particularly appealing if you already have a reason to run at least part of your system in-house, like Big Data that would cost a fortune to store in the public cloud.
Cloudbursting Technology implementation is challenging:
- You have to keep two asynchronous systems in lockstep across the public Internet
- ensuring security of the Application
- handling unpredictable latency
- And permanently optimizing for data locality
This Video Webinar, recorded for free, is to learn how this can actually work with Amazon EC2 and SQS. The implementation is based on RoR and Resque/Redis, but the concepts are broadly applicable.
The term Cloudbursting that was developed several years ago for exploiting extreme elasticity was “cloudbursting.” When an enterprise runs into an unanticipated surge in demand for a certain application or business service, the story goes, it should be able to quickly harness gobs of extra capacity in the cloud to keep its app from overloading and then melting down.
Typical scenarios include e-commerce and mobile marketing, which each involve fickle and potentially big crowds of consumers. Say it’s December and an online retailer experiences a flood of visitors to its site. Instead of risking an overload, it could harness as much cloud infrastructure as it needed, and for only as long as it needed. Visitors to its site would be none the wiser, and the cloud capacity could be shed as soon as demand dropped back to normal.
Alas, for the most part, cloudbursting turns out to be more mythical than actual. On paper, it’s a great idea, but in reality, pushing apps up into the cloud at a moment’s notice, or even a day’s notice, is non-trivial. Despite what many avid cloud proponents say, there’s still a good amount of configuring and preparation required to get cloud infrastructure ready to run anything but the most trivial apps. And unless the terrestrial and cloud technology stacks are closely matched to begin with, there’s little chance of moving an app from one to the other.
See also: http://www.bestechvideos.com/2012/02/22/surge-2011-cloudbursting-with-amazon-ec2-and-sqs