Hybrid Cloud's Burst Bubble

Upcoming Events

Interop is the only event to give you a comprehensive and unbiased understanding of all the latest innovations-including cloud computing, virtualization, security, mobility and data center advances-that help position your company for growth.

Register Now!

Tags: hybrid cloud, private cloud, cloud computing

Channel: Private Cloud, Cloud Computing, Public Cloud

See more from this blogger

Posted by Joe Onisick
December 07, 2011

One of the more hyped use-case examples for hybrid cloud is cloud bursting. And why not? It's truly the have-your-cake-and-eat-it-too scenario. During normal business operations, your systems run in-house on private cloud infrastructure, and during unforeseen or unpredictable peaks, your services burst to excess capacity at your public cloud provider(s) of choice. It's IT utopia, right? It’s the comfort of maintaining your own systems with the insurance of endless available capacity for the unknown.

At this point, geeks, managers and execs alike jump straight into the "how" of getting it done. Whiteboards are drawn, erased and drawn again, vendor phone calls are made, and, repeatedly, ‘Yes, we can help with that’ or ‘Our product does that’ is heard. I’ve participated in these same discussions, merrily frolicking into the "how" thought experiment without stopping to think about the ever-more-important "why." Why would I want to burst? What business advantage would I gain? Is bursting the right solution to the problem of capacity? Will bursting help me accomplish my organization's mission?

The answer to those questions will most typically be no, but don’t take my word for it, instead join me on a thought experiment:

First, let’s set a very generic and loose list of design requirements for your bursting services and applications:

Must be designed for compatibility with the public cloud provider(s) of choice

Must be designed so that all or some portion can be run in that chosen cloud provider

Must be within acceptable performance tolerance when servicing over the WAN via said cloud provide.

Must meet security and compliance regulations while hosted in public cloud

OK, base requirements are defined, and easy enough to meet. In fact, plenty of people are meeting those requirements for their services. Those people are now happily running their applications in, wait for it, public clouds. My question for you for part one of our experiment: If your app is designed for, and compliant with, public cloud deployment, why are you rolling out infrastructure for it internally?

Of course, you could answer with things like legacy investment protection, which does have a play. In those cases, you’ll need to assess whether the hardware/software investments you’re using to make that legacy hardware into a public-cloud-compatible private cloud are worth it for a service that can go straight to the cloud. Could you push that application to the cloud and migrate a non-cloud-friendly legacy app or latency-sensitive app to the existing hardware?

Joe Onisick is the Founder of Define the Cloud. You can follow his angry rants at www.definethecloud.net or on Twitter @jonisick.

Page: 1 | 2 |Next Page »

More Insights


	To upload an avatar photo, first complete your Disqus profile. \| View the list of supported HTML tags you can use to style comments. \| Please read our commenting policy.

Private Cloud Reports

Automation & Orchestration: Prepare for Successful Deployment

Automation and orchestration technologies can make IT more efficient and better able to serve the business by streamlining common tasks and speeding service delivery. But it doesn't always go as smoothly as we'd like. In this report, we outline the potential snags and share strategies and best practices to ensure successful implementation.

Bending the 80/20 Barrier: Automation Is Just the Start

As the economy recovers, IT is caught in a squeeze between requests for new applications, services and device support and demands from upper management to keep budgets lean, staffing light and operations tight. These are irreconcilable objectives as long as we spend the vast majority of our resources on legacy services -- a variant on the familiar 80/20 rule, whereby 80% of IT's time, effort and dollars are spent on routine "keep the lights on" activities with only 20% going to develop new services and applications.

Fundamentals: Usage-Based Accounting

It's a trend we're seeing in surveys and interviews across the technology spectrum: Business executives expect IT to act like a nimble embedded enterprise, responsive to rapidly changing technology needs-more Google, less Post Office. That's the whole point of building a private cloud. But the other part of that equation is getting granular with costs. In this report, we chart the new service-oriented IT landscape and provide a guide to the key components: service catalogs, cost and pricing models, and financial systems integration.

Research and Reports

FEATURED RESEARCH

State of Server Technology

FEATURED STRATEGY

The Long-Distance LAN

Register for Network Computing Pro

Find hundreds of reports featuring research from your peers, and best practices from top IT pros.

Video

Joe Onisick

Tech Centers

Channels

Bloggers

Upcoming Events

Interop NY Oct. 1-5

Subscribe to Newsletter

Vendor NewsFeed