Last week's outage at Amazon's Northern Virginia datacenter is the topic de jour for the tech industry this week. There seems to be two major categories of blog posts, those that blame the customers for not constructing a geo-redundant, high-availability environment and posts that blame Amazon for the failure. The truth is somewhere in middle, I concur with Lou Honick that customers have a responsibility to purchase and configure a highly available environment. Additionally, O'Reilly called it the "the cloud's shining moment" and put the blame squarely on customers. There is however ample evidence that customers who tried to architect a HA environment based on Amazons recommended best practices (configuring redundant services in multiple availability zones) discovered that the service didn't work as Amazon advertised. There is a great post on ReadWriteCloud which thoroughly documents these missteps and the technology issues experienced by AWS during the process. Based on how these events have unfolded I predict that we will see four significant changes in cloud computing moving forward, they are as follows:
Customers will demand strong Service Level Agreements - The SLA at Amazon is particularly weak, in fact based on last week's events Amazon doesn't owe its customers a dime in SLA credits. While an SLA credit doesn't begin to compensate customers for the losses that their business may incur from an outage, a 100% uptime guarantee is becoming very common with high quality hosting companies and it provides proper peace of mind to customers. It tells customers that their vendor believes in the service they are offering.
domain hosting sites domain hosting srvcs domain hosting wikipedia download anti ddos software download ddos attack tutorial
কোন মন্তব্য নেই:
একটি মন্তব্য পোস্ট করুন