Excessive supply of cloud markets: an expensive cloud computing error

When http://www.aliyun.com/zixun/aggregation/10145.html "> Enterprise Architects and IT professionals run the IT infrastructure in a PAAs or IaaS cloud, such as in the Amazon Web Services (AWS) cloud , what is the most expensive mistake? The problem, according to Cloudability's chief operating officer Pete Adams, is the procurement paradox: those responsible for managing operators don't buy more of this, or buy less.

The harm of excessive supply

What is the DevOps team buying too much? Simply, they often buy too much cloud computing power. "People are too much in the infrastructure to buy power only when they need it, but the cloud allows you to automatically expand the infrastructure when you need it," Adams said. It's an old habit that's hard to get rid of, historically, IT departments must create large enough systems to handle peak demand. But that's not the way you provide the necessities in the cloud. In the cloud, your product is provided on demand and allows cloud vendors to cope with occasional spikes. "Excess supply is a cost you don't need to incur," he said.

Optimistic treatment of elastic computing cloud retention instances

What is another expensive mistake that most AWS customers are causing? The second mistake is that people buy to keep the instance a bit slow, which is Amazon's lower infrastructure cost per hour, in exchange for early repayment, Adams said. Buying a reserved instance but refusing to pull the trigger is not the only way Amazon fills it, but it touches on the bottom line of many AWS customers.

So why don't more people buy retention instances? This is because it is tiring to find out which type of retention instances are to be purchased, and worry that they may make a mistake and produce more costs rather than cost savings. "There are over 2000 different types of retention instances available for users to purchase, depending on the type of instance, the available areas you buy, and the operating system, each reserved instance has a different break-even point," Adams said. As more and more parameters are chosen for the appropriate retention instances, many organizations simply opt out of the decision to avoid making the wrong decision.

(Responsible editor: The good of the Legacy)