Knowing exactly how much and what type of cloud service a company needs is one of the more challenging aspects of deploying a cloud strategy, and most enterprises are getting it wrong, according to experts.
"The whole premise of the cloud should be to drive the IT director to think small, but people aren't doing that," says Sharon Wagner, president of Cloudyn, an Israeli company whose SaaS application helps businesses monitor their cloud usage and provides recommendations on how to right-size it. "Many customers are over provisioning, which leads directly to over paying."
[ Also on InfoWorld: Amid doubts about cloud file-sharing services, enterprises operate their own. | In the data center today, the action is in the private cloud. InfoWorld's experts take you through what you need to know to do it right in our "Private Cloud Deep Dive" PDF special report. | Also check out our "Cloud Security Deep Dive," our "Cloud Storage Deep Dive," and our "Cloud Services Deep Dive." ]
Experts agree. "I think it's a problem just about everyone could be facing," says Paul Burns, an independent cloud analyst at Neovise. Burns believes there is somewhat of a misnomer about paying for cloud services. While many consumers think they are paying for resources they use in the cloud, instead users are actually paying for a certain capacity of compute or storage. Whether they use it or not is up to them.
"Just about every customer likely has an issue with this," says James Staten, a vice president and principal analyst at Forrester. "Some have had that shock bill from their service provider so they've gotten pretty good at dealing with it, but almost everyone could benefit from taking a closer look at their actual usage."
So what can be done about overprovisioning of resources? Companies can fairly easy install measures to prevent it, Staten says. The best way is by having load balancers written directly into application code that automatically scale up and down resources based on need. Just as important as scaling up though is scaling back down when those resources are no longer needed. Staten warns, however, that enterprises can run into some complications. A bug in a software or a distributed denial-of-service attack can, for example, create false scaling requests for additional resources.
Overprovisioning occurs mostly in infrastructure-as-a-service and platform-as-a-service instances because those are metered based on an amount of compute or storage, Wagner says. Software-as-a-service offerings traditionally don't have as much of a problem with the issue because they are generally charged on a per-user basis.