Cloudbursting A.k.a. Overdrafting, Reverse Cloudbursting and Cloud Balancing

Cloudbursting

A.k.a. Overdrafting, Reverse Cloudbursting & Cloud Balancing

One of the most heavily discussed topics in cloud computing is that of cloudbursting or cloud balancing as it is often called. Cloudbursting is essentially a load balancing measure or set of measures that seeks to accrue more resources for a cloud (or cloud user) that has exceeded their hardware / bandwidth limitations. By most accounts, cloudbursting only becomes a necessity in times where peak levels of traffic are experienced across an entire cloud network. Because this type of situation is infrequently encountered, many organizations simply opt to temporarily requisition their additional cloud hardware / resources (offsite or from another provider). It simply doesn't make sense for most organizations to purchase additional resources just to cover these overdraft periods (because they wouldn't be used at any other time), and by 'renting' additional resources they are able to save quite a lot of capital.

How does cloudbursting work?

Once the limits of a cloud network have been reached (in terms of storage space or computing power) requests are sent out to other requisitioned servers to make up the difference. One of the current limitations of this new model is a lack of proper management software tools that can create tiers for data streams so that newly requisitioned resources can be implemented. In other words, cloudbursting is sort of a 'work in progress'. As it currently stands, cloudbursting may be best used as a form of temporary offsite data storage; all integral processes and virtualization might be better handled on-site or via the chief cloud services provider.

Security concerns of cloudbursting

One growing area of concern around cloudbursting is that of security; more specifically, can it be guaranteed? The security around cloudbursting is not as solid as what is found in a typical cloud environment. That's not to say that it can't be secured using the same methods employed by large scale cloud service providers; it's just that at the current moment it's not. This is the reason why many specialists in the field of cloudbursting recommend it for non-critical processes that do not include the use or transfer of sensitive data / information. So basically, applications that don't involve a complex:

• Infrastructure
• System / series integration
• Set of internal structures that are vital to the core data center
• Application delivery structure
• Series of components

For retail and / or eCommerce businesses, using cloudbursting must be approached very carefully. Resigning customer data to a public cloud could lead to an eventual leak of data. And there's no better way to lose face than by letting customer information and data fall into the wrong hands.

How does Cloudbursting differ from IaaS or PaaS?

Many individuals may be quick to draw comparisons between established types of cloud services such as Infrastructure as a Service or Platform as a Service (which both essentially offer cloud users access to an array of hardware resources). The difference is that cloudbursting is done to supplement the software structures that have already been established by a service or private cloud. Cloudbursting is not a permanent solution in this sense, just a temporary fix. It is for this very reason (lack of runtime and software resources) that cloudbursting should be regarded as a more affordable solution than a conventional upgrade of service or hardware.

Incompatibility Issues

Another potential problem with cloudbursting is the incompatibility of the various runtime environments or components of the host network and the cloudbursting one. The typical workaround in these types of situations involves the use of hybrid environment management tools. But whether or not this will work properly is dependant on the platform that both clouds are operating on (they are usually required to be utilizing the same platform).

Cloudbursting is an excellent way to supplement your current cloud network or hosted cloud services in times of need; but as your business / organization continues to expand it may only be a temporary fix. Excessive implementation of cloudbursting is a definite signifier that additional hardware resources need to amassed or a more extensive / encompassing cloud service plan must be adopted. However, in the short term cloudbursting remains an excellent solution for supplementing networks that operate within the realms of retail or eCommerce sales. Many cloud providers are extending their services to include 'hybrid cloud' capabilities so that cloudbursting will no longer be an issue of concern among their customers.

+++

Would you like to learn more about Cloud Computing and how to manage your IT Service through Cloud technology? Sign up for our Cloud Computing Foundation Program. Now also available for iPad and iPhone.