Recently Amazon's EC2 service has experienced a bit of a hiccup (to put it mildly) and as I've been reading through samples of the coverage a few thoughts have been occurring to me. Judging by the articles I've read to date, it would appear that there's something in there for everyone with a thought/stake/opinion on cloud services.
The naysayers now have a new example to point to when they look for a reason to reject moving any operations into the cloud and those in support of cloud have a new hurdle to overcome. I've got a feeling a whole new series of negative ads will be following from cloud service providers that want to let us all know exactly why this could never happen to them.
The likely reality is that availability and uptime that can be achieved through a cloud service provider would still far outpace anything the majority of those pointing at the current incident as reassurance that keeping all services in house has been the right thing to do.
Any service interruption at the provider level is going to reveal its fair share of overly enthusiastic adopters who have pushed the limits of what would should reasonably be entrusted fully and completely into the cloud. In response, expect an upcoming series of soapbox articles to come out of the security geek peanut gallery pointing out the series of #fail.
As always, blindly dismissing or trusting any solution without performing your own due diligence seems silly. Learn to make the most of the information that is being released but also try to filter out the noise and the hype and consider the real implications to your specific situation.
No comments:
Post a Comment