Commentary

Michael Hickins
 

Gmail Outage Says More About Google Than Clouds

The hand-wringing over yesterday's Gmail outage was as predictable as it was wrong-headed.

The hand-wringing over yesterday's Gmail outage was as predictable as it was wrong-headed.Yes, as many observers were quick to point out, this was Gmail's fifth significant outage of the year. But what most of them fail to say is that their own systems are probably even more unreliable. According to Osterman Research, most enterprise email systems go down for almost an hour per month:

in mid-sized and large organizations, email systems experience a mean of 53 minutes of unplanned downtime during a typical month. That means that during a one-year period, a typical email system will be down for 10.6 hours.

More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Those numbers confirm what most of us who have worked in corporate environments since before the advent of cloud computing already know, which is that internal systems are no more reliable. But to be fair, what gets most people hot under the collar about cloud computing is the helpless feeling that comes with not being able to call their IT guy and scream.

What it comes down is the illusion that if you have a system behind your firewall, it's under your control. Well, it's under your control to the extent that you're the system administrator, and that you can deal with the problem rather than fielding angry calls from the C-suite, and that the person who knows this system isn't on vacation or on break or in the subway.

True story. My wife, a former professional race car driver -- drives really fast on tracks designed to let you skid around turns -- is afraid of flying on commercial airlines. Because she's not driving the things. She's not in control. Never mind that the fleet is serviced by highly-skilled technicians who know the lives of thousands are in their hands, and piloted by highly-experienced people who have their own lives in their hands, as well as all the passengers and crew's.

Does Google have a couple more engineers than your average Fortune 500 company? Does it really seem like they'd do a better job if someone were screaming in their ear, demanding to know when "the email will work again?"

So am I trying to say we should just grin and bear it, as we did with our local ISPs in the days before broadband? Not a chance.

The cloud means we have choices. There's still Yahoo mail, after all, not to mention Windows Live, both of which are in the process of developing services that make Web-based email more than just an asynchronous communications tool by integrating features like social networking and document handling capabilities.

Large systems vendors are also promoting the idea of the private cloud, which although self-serving to those vendors, does provide enough scale (from a manpower perspective) to make the idea of taking email (and other computing services) outside the firewall an attractive proposition.

Yesterday's outage doesn't bring the reliability of the cloud into question. It does bring Google's reliability into question.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links