The following text is
copyright 2013 by Network World, permission is hearby
given for reproduction, as long as attribution is given and this notice is included.
Cloud
services: Computus Interruptus
By
Scott Bradner
I
use Google Docs as part of my day job.
This morning I accessed a file and updated it but when I went back a
short time later I got a "502" error page -- something had gone amuck
in Google land. Everything seemed
to work when I tried a few hours later but the incident was a forceful reminder
of one of the important features of cloud services - when they go down so do
you.
The
message I got was less than helpful:
"502. That's an error.
The server encountered a temporary error and could not complete your
request. Please try again in 30
seconds. That's all we
know." It was a lot longer
than 30 seconds before things worked again.
This
was not a major outage for me and I had no trouble finding other things to do
with my time but I wonder what the impact was on the few million other people
who also had to find things to do other than what they originally planned.
Google Docs has been generally reliable but its users have suffered some disruptions of service over the years. (See here (http://www.networkworld.com/news/2012/110612-google-outage-264023.html) , here (http://www.networkworld.com/news/2012/121012-gmail-outage-264956.html) and here (http://www.networkworld.com/news/2012/060712-gmail-outage-likely-hit-several-259988.html).)
Other cloud service providers have had much worse problems. Some of Microsoft's services were off the air for a good chunk of a day last week (http://www.networkworld.com/news/2013/031413-microsoft-outlook-outage-267705.html), an administrative mixup caused a days outage of the Microsoft Azure cloud service back in February (http://www.networkworld.com/news/2013/022313-microsoft39s-azure-service-hit-by-266977.html) with a similar problem a year ago (http://www.networkworld.com/news/2012/022912-microsofts-azure-cloud-suffers-serious-256777.html). Amazon has had numerous and significant outages. (See here (http://www.networkworld.com/news/2012/102312-amazon-outage-263617.html), here (http://www.networkworld.com/community/blog/amazon-says-its-getting-handle-ec2-outage) and here (http://www.networkworld.com/community/node/73265)).
In the face of this semi-reliable technical world Microsoft
is trying to convince
us all that the cloud is a great place to live. Office 365 offers a passel of cloud-based services. Microsoft wants us to think that Office
365 represents the future as being anchored to a cloud rather than to a
machine. There is something
attractive in that vision as long as you trust the solidity of the cloud and
the cloud vendor. Microsoft's
Office 365 cloud is not perfect (http://www.networkworld.com/news/2012/111412-office-365-outage-264261.html)
but seems to have been generally reliable.
I guess
I'm a bit of an old fart stuck in my ways. I do use cloud services, including Google Docs, but I use
them for collaboration not for original creation. I do the creation on my own computers, where I control the
access and, to some degree, the reliability, before transferring the result to
the cloud for group development. I
do my own backup of the material on my systems so I am not toast if a company
goes out of business (http://news.cnet.com/2100-1023-802658.html) or changes
business models (http://news.cnet.com/8301-13578_3-57559710-38/instagram-says-it-now-has-the-right-to-sell-your-photos/).
Maybe I like the illusion of control but I am not yet ready to let go and float. The worry of what might happen when human or other failures turns off the anti-gravity machine, and the worry of who thinks they own what I write and do make me not yet ready to trust wholeheartedly in the fog that is the cloud.
disclaimer: Harvard is exploring and using a lot of cloud-based services. I do not know the level of comfort the average university user has in these developments nor has the university yet made any particular affirmation of trust so the above distrust represents my own feelings.