Watch as I awkwardly stumble through life

A geek`s perspective on cloud hosting

Posted by Marius Voila on August 31, 2010 in London, U.K . — 0 comments This post contains 504 words

The term “cloud hosting” has become more popular over the past few years and it seems like everyone is talking about it. I’m often asked by customers and coworkers about what cloud hosting really is. Where does traditional dedicated hosting end and cloud begin? Do they overlap? Who needs cloud and who doesn’t?

You can’t talk about cloud hosting without defining it first. When I think of “cloud”, these are the things that come to mind:

That list may seem a bit vague at first, but try to let it sink in just a bit. Hosting applications in a “cloud” shouldn’t mean that you must have a virtual instance running on Xen, KVM or VMWare, and it shouldn’t mean that you must have an account with Rackspace Cloud, Amazon EC2, or Microsoft Azure. It means that your hosting operations are highly automated and you can rapidly allocate and deallocate resources for the requirements of your current projects.

Consider this: a customer of a traditional dedicated hosting provider decides to take their applications and host them on one VPS at a leading commercial provider. That provider allows the customer to spin up new VM’s in a matter of minutes and re-image the VM’s whenever they like. Is that cloud hosting? I’d say yes – even if it’s one single virtual instance. That customer has moved from a hosting system with manual interventions and extended lead times to a system where they have instant control over their resources.

It’s not possible to talk about what cloud is without talking about what it isn’t.

It’s important to remember that cloud hosting is a marketing term. As for the technology of cloud, it’s what you make of it. You should be looking to reduce costs, solidify availability and increase performance every day. If the ideals of cloud hosting help you do that, it might be the right option for you.