With IBM, Amazon and Microsoft fighting for our cloud computing attention, we might forget to think about useful scenarios for all this fancy airy stuff. We all know the classical e-commerce example with its season-bound resource spikes and the occasional raw processing/render power we need, but this week I stumbled upon something new: cloud bursting. Before I get into that, let’s first take a little step back. A recent blog post by James Urquhart (now helping Cisco in cloud computing strategy) lets us wonder whether a cloud computing strategy is always cheaper than having your own data center. As you might have guessed: no. The main idea is that applications that are always running on 100 % are often hosted cheaper in your own data center than paying for the elasticity of a cloud (which you actually don’t use). So, applications that do need the elasticity (e.g. the e-commerce and render farm we talked about earlier) can benefit financially from the cloud. One other strategy that I didn’t think of earlier (stupid me) was pointed out on Scobleizer’s post of his visit to the Cisco data center: cloud bursting. Simply said: run everything in your own data center and once you detect heavy usage, offload it to the cloud! Example he gives is 12seconds.tv that offloads a movie to Amazon’s S3 file storage when they detect high view rates. Can we think of any useful applications in the enterprise space? Oh yes: update / file servers (it only gets busy when you release a new product or service pack), payroll processing (only once a month, but do you want this in the cloud?), … Any other suggestions?
Is the cloud bursting?
L. Provoos
5 Comments
Category :
5 Comments
Leave a comment
Lee:
Certainly the ability to address peak loads tied to business cycles (month-end closing is another example) is a prime example, where we tend to have a significant amount of critical infrastructure sitting around doing nothing. Its also useful to note that you probably want to still handle business critical workloads in-house and use cloud-busting to handle tier 2 and tier 3 workloads.
A different example is using cloud busting to handle short-term power and cooling challenges, such as the perpetually imminent brownouts we seem to have in California on hot summer days--again, you could transfer lower priority workloads off-prem, or alternatively, you could transfer critical workloads somewhere that's not having power challenges.
Finally, there is always the business continuance aspects of having some elastic capacity available to deal with unforeseen events.
Omar Sultan
Cisco
Certainly the ability to address peak loads tied to business cycles (month-end closing is another example) is a prime example, where we tend to have a significant amount of critical infrastructure sitting around doing nothing. Its also useful to note that you probably want to still handle business critical workloads in-house and use cloud-busting to handle tier 2 and tier 3 workloads.
A different example is using cloud busting to handle short-term power and cooling challenges, such as the perpetually imminent brownouts we seem to have in California on hot summer days--again, you could transfer lower priority workloads off-prem, or alternatively, you could transfer critical workloads somewhere that's not having power challenges.
Finally, there is always the business continuance aspects of having some elastic capacity available to deal with unforeseen events.
Omar Sultan
Cisco
Our company is addressing Omar's last point- DR in the cloud. Using cloud-savvy async replication to multiple cloud nodes (or providers) we determined in one scenario the following:
- traditional DR (4TB, replicated everything) would cost $897K over 3 years, and would provide an expected 99.998% uptime.
- cloud DR using TwinStrata to-be-released product would provide an expected 99.997% uptime- but at 1/3 of the cost over 3 years.
We're still stealth with detail, but would be happy to discuss more offline.
Craig
challiwell@twinstrata.com
415.244.6671
- traditional DR (4TB, replicated everything) would cost $897K over 3 years, and would provide an expected 99.998% uptime.
- cloud DR using TwinStrata to-be-released product would provide an expected 99.997% uptime- but at 1/3 of the cost over 3 years.
We're still stealth with detail, but would be happy to discuss more offline.
Craig
challiwell@twinstrata.com
415.244.6671
Our company is addressing Omar's last point- DR in the cloud. Using cloud-savvy async replication to multiple cloud nodes (or providers) we determined in one scenario the following:
- traditional DR (4TB, replicated everything) would cost $897K over 3 years, and would provide an expected 99.998% uptime.
- cloud DR using TwinStrata to-be-released product would provide an expected 99.997% uptime- but at 1/3 of the cost over 3 years.
We're still stealth with detail, but would be happy to discuss more offline.
Craig
challiwell@twinstrata.com
415.244.6671
- traditional DR (4TB, replicated everything) would cost $897K over 3 years, and would provide an expected 99.998% uptime.
- cloud DR using TwinStrata to-be-released product would provide an expected 99.997% uptime- but at 1/3 of the cost over 3 years.
We're still stealth with detail, but would be happy to discuss more offline.
Craig
challiwell@twinstrata.com
415.244.6671
Hi Omar, Really love this insight with the California electricity thing! Never thought about that :-)
Btw nice job that you guys hired James Urquhart, that man is good!
Lee
Btw nice job that you guys hired James Urquhart, that man is good!
Lee
Hi Craig, very interesting, will drop you an email tomorrow on that!
Lee
Lee


















