<?xml version="1.0" encoding="iso-8859-2"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:series="http://unfoldingneurons.com/"
	>

<channel>
	<title>Fractured Bloughtsgoogledoc | Fractured Bloughts</title>
	<atom:link href="http://fracturedbloughts.rolandhesz.com/tag/googledoc/feed/" rel="self" type="application/rss+xml" />
	<link>http://fracturedbloughts.rolandhesz.com</link>
	<description>Musings about work and life</description>
	<lastBuildDate>Mon, 10 May 2010 19:52:08 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4-alpha-19827</generator>
		<item>
		<title>Cloud computing brings us rain</title>
		<link>http://fracturedbloughts.rolandhesz.com/2008/07/23/cloud-computing-brings-us-rain/</link>
		<comments>http://fracturedbloughts.rolandhesz.com/2008/07/23/cloud-computing-brings-us-rain/#comments</comments>
		<pubDate>Wed, 23 Jul 2008 07:15:00 +0000</pubDate>
		<dc:creator>Roland Hesz</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[amazon s3]]></category>
		<category><![CDATA[Cloud computing]]></category>
		<category><![CDATA[desktop application]]></category>
		<category><![CDATA[downtime]]></category>
		<category><![CDATA[googledoc]]></category>
		<category><![CDATA[linkedin]]></category>
		<category><![CDATA[uptime]]></category>
		<category><![CDATA[zoho]]></category>

		<guid isPermaLink="false">http://fracturedbloughts.heszroland.hu/?p=165</guid>
		<description><![CDATA[So cloud computing. Moving on the web, who needs desktop application, lets head back to the golden age, when a server was a server, and a terminal was a terminal. I don&#8217;t know, I&#8217;ve never been the fan of the put everything in the browser and &#8220;fly me to the clouds&#8221; movement, for several reasons....]]></description>
			<content:encoded><![CDATA[<p>So cloud computing. Moving on the web, who needs desktop application, lets head back to the golden age, when a server was a server, and a terminal was a terminal.</p>
<p>I don&#8217;t know, I&#8217;ve never been the fan of the <a href="http://fracturedbloughts.heszroland.hu/2006/10/10/webrowser-based-application-is-it-mandatory/">put everything in the browser</a> and <a href="http://fracturedbloughts.heszroland.hu/2008/03/23/desktop-or-web/">&#8220;fly me to the clouds&#8221;</a> movement, for several reasons. First, in my opinion the web browser is called browser and not &#8220;advanced data manipulation and browsing and knitting interface&#8221; for a reason.</p>
<p><span id="more-165"></span></p>
<p>The second is that well, if you put everything in the cloud, what do you do when it starts to rain? <a href="http://www.25hoursaday.com/weblog/2008/07/21/SomeThoughtsOnAmazonS3sRecentOutage.aspx">Dare Obasanjo certainly has a point</a> that a 99.9% uptime means almost 9 hours of downtime a year. <a href="http://www.readwriteweb.com/archives/more_amazon_s3_downtime.php">Some posts  are not really using the same math</a> as I do, they calculate with a worse service level, and that completely undermines the complaint (99% uptime means almost 88 hours of downtime a year, so 6 hours is not that bad). And if you are here, go and <a href="http://gigaom.com/2008/07/20/amazon-s3-outage-july-2008/">read Om Malik&#8217;s opinion</a>, he has a long post on the topic.</p>
<p>So, Amazon is promising almost 9 hours of downtime. If that 9 hours happen to arrive on a quiet Sunday &#8211; or over several quiet Sundays &#8211; then it&#8217;s no problem really.</p>
<p>But what do you do if that 9 hours drive accross the last day of a critical project phase?<br />
I like the idea of cloud computing, and I don&#8217;t want to say that you should not use <a href="http://amazon.com/s3">Amazon S3</a>, or <a href="http://zoho.com/">Zoho</a> or <a href="http://docs.google.com">GoogleDoc</a>, or whatever service you are using. I just would like to know what will happen to your service when the cloud gets dark?</p>
<p>On LinkedIn there was a question on why people want technical documentation in PDF, on paper, in Word, when all information can be put on internal wikis, blogs, etc. Most of the answers pointed to the neccessity to reach the things offline.</p>
<p>And not only when the server goes down. Interesting thing <a href="http://www.linkedin.com/redirect?url=http%3A%2F%2Fwww%2Ejibberjobber%2Ecom%2Fblog%2F2008%2F07%2F17%2Flinkedin-maintenance-do-this-right-now-or-else&amp;urlhash=pGWv">I read on JibberJobber</a>, <a href="http://linkedin.com">LinkedIn</a> for example does not have a backup of your profile. If it disappears for whatever reason, you are toast. Have to start from scratch. That&#8217;s a good reason to save all your contacts, and your profile on your PC regularly &#8211; i.e. whenever there is a change.</p>
<p>Internet access is not 100% around the world, and the internet does not have 100% uptime. Bits go down regularly. I bet there are a couple intranets down even right now. Also there are 3 things in life that are certain: death, taxes and data loss.</p>
<p>I don&#8217;t talk against cloud computing &#8211; who am I to talk against it anyway -, I just want to point out that when you go near the clouds, you better have an umbrella, just in case.</p>
]]></content:encoded>
			<wfw:commentRss>http://fracturedbloughts.rolandhesz.com/2008/07/23/cloud-computing-brings-us-rain/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
	
		<series:name><![CDATA[Cloud computing]]></series:name>
	</item>
	</channel>
</rss>

