#googlefail

Google failed! Read all about it!

Sure, it's all over the news, Tuesday's Google major glitch, impacting about 14% of its global user base was embarrassing, disappointing and plain dumb.

And of course, the question now arises: How good of an idea really is cloud computing when even Google can go down?

Well, let's think about it, what are the alternatives to cloud computing? Are they really better in terms of availability?

Because that's the real question, in terms of general availability, who is going to be better equipped to respond to the glitches we know there will be: a company that doesn't specialize in IT infrastructure but merely uses them or the cloud provider – a company that specializes precisely on IT infrastructure?

No matter how you look at it, non specialized staff in a non specialized company will always react slower, take more time to figure it out that its specialized staff counterpart in the specialized company, this doesn't just applies to cloud computing but to the fastest growing trend in business in the past 50 years, outsourcing.

We just have to keep in mind that cloud computing is not going to give us 100% availability, but, big surprise, nothing is! We all know the benefits of cloud computing; and now here we have one of the issues with cloud computing, not a small one, but not a new one either!

Google failed, AWS failed, the question is, did your own IT infrastructure ever failed on you?

Note that we are not claiming this should be taken lightly, a failure in your IT infrastructure provider should worry you, but what's most important than an actual failure is how they respond to it: did they disregard users' complaints? Did they know about it before you did? This aftermath should be the one leading our decision-making process when choosing a cloud provider.

We just need to remember, #googlefail'ed, and so will your IT infrastructure provider.