Cloud Computing News

Making the move from on-premises applications and data storage to cloud-based applications and data storage is a big step, and one of the first things that comes to mind is access. “Can I get to my data and apps?” “Will there be latency and delay?”

These are important questions. In the old days of centralized mainframe computing, and in the early days of networking, latency was common. Data entry people suffered productivity loss because they had to wait for processing on the back end before they could enter more data; applications were less responsive; and web surfing when the web was new could be a frustrating experience. Remember the first time you tried to access a graphical web site over a dial-up line? We think of those experiences and imagine cloud computing to be more of the same.

But the fact is, broadband access and gigabit-speed networking has changed all that, and the widespread access of broadband is the natural precursor of widespread cloud computing.

The details: How to buy it
We’ve painted a broad picture now of cloud computing, what it is, what it does, and how it helps us. But once you’ve made the decision to deploy cloud technology, then all of a sudden you’re faced with the details. RFPs, needs analyses, sorting through the different vendors, watching their presentations and making a decision.

The process is the same as with any other type of technology. Determine what you need, put out an RFP, create a short list, and look at the offers. But one of the most important elements of purchasing cloud services is the service level agreement (SLA). An SLA has long been an important aspect of any sort of IT service, but in the era of the cloud, it becomes even more vital since so much more depends on the service.

The first thing to evaluate is whether the cloud service provider offers an SLA, and what the details of it may be. There are performance promises that are nothing more than marketing fluff: “Great service or your money back!” And then there are performance promises that have teeth. The SLA should include in specific language, at least the following:
• Expected performance levels should be laid out in specific terms.
• Uptime percentage must also be stated in specific numeric values.
• Response time should also be stated in specific terms.
• The provider should also provide for consequences if the terms are not met; for example, a penalty, free service for a period of time, etc.
• The SLA may also set out specific tasks and deliverables, such as reports or other functions.

Most cloud providers will offer a boilerplate SLA, and this may well be adequate—but if you are a large customer, tweaking the terms of the SLA is common. In some cases, the terms are negotiable.

Cloud providers, and other types of providers as well, have embraced the value of the SLA, not just because it delivers value to the customer, but for their own uses as well. From the perspective of the provider, it protects against escalating client expectations. For example, some services may deliver varying levels of guarantees, each one with a different rate. There may be for example, one price for a 98 percent guarantee, and another for a 99 percent guarantee.

_______________________________________________

This blog is brought to you by Virtual Global; provider enterprise-class cloud computing solutions.  Since 1995, our technologies have helped commercial and federal customers worldwide with their enterprise IT needs.