<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Tim O&#8217;Reilly vs. Nick Carr</title>
	<atom:link href="http://markusklems.wordpress.com/2008/10/30/tim-oreilly-vs-nick-car/feed/" rel="self" type="application/rss+xml" />
	<link>http://markusklems.wordpress.com/2008/10/30/tim-oreilly-vs-nick-car/</link>
	<description>Random Thoughts of Markus Klems</description>
	<lastBuildDate>Sun, 08 Nov 2009 02:36:18 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Markus Klems</title>
		<link>http://markusklems.wordpress.com/2008/10/30/tim-oreilly-vs-nick-car/#comment-139</link>
		<dc:creator>Markus Klems</dc:creator>
		<pubDate>Thu, 30 Oct 2008 18:18:34 +0000</pubDate>
		<guid isPermaLink="false">http://markusklems.wordpress.com/?p=127#comment-139</guid>
		<description>You are certainly right that time to market is a crucial issue and that in the end you only need an infrastructure that scales up if your applications and services are successful. On the other hand, one could argue that &quot;Failure&quot; is an equally important issue as &quot;Success&quot;. If you cannot scale your service down when it becomes unpopular (or isn&#039;t needed anymore at all, such as with Websites for one-time events), you are stuck with your CapEx.

The thing is that in a somewhat open environment, that allows third-party developers, like RightScale, to join the game, innovation does not depend so much on the Cloud Computing provider. The provider can concentrate on core IaaS issues and let others care for the tools and frameworks.

Thanks for your comment.</description>
		<content:encoded><![CDATA[<p>You are certainly right that time to market is a crucial issue and that in the end you only need an infrastructure that scales up if your applications and services are successful. On the other hand, one could argue that &#8220;Failure&#8221; is an equally important issue as &#8220;Success&#8221;. If you cannot scale your service down when it becomes unpopular (or isn&#8217;t needed anymore at all, such as with Websites for one-time events), you are stuck with your CapEx.</p>
<p>The thing is that in a somewhat open environment, that allows third-party developers, like RightScale, to join the game, innovation does not depend so much on the Cloud Computing provider. The provider can concentrate on core IaaS issues and let others care for the tools and frameworks.</p>
<p>Thanks for your comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Edward M. Goldberg</title>
		<link>http://markusklems.wordpress.com/2008/10/30/tim-oreilly-vs-nick-car/#comment-138</link>
		<dc:creator>Edward M. Goldberg</dc:creator>
		<pubDate>Thu, 30 Oct 2008 17:45:45 +0000</pubDate>
		<guid isPermaLink="false">http://markusklems.wordpress.com/?p=127#comment-138</guid>
		<description>I enjoyed this post,  your point that the Developer Facing effect are the important ones IMHO misses a very important issue.

Success.

For Cloud Deployments the best feedback for the growth of the idea continues to be that it works.  Time to market is a very key feature that we tend omit talking about.

What the users see is applications sooner that stay working under loads that vary wildly over time.  This is a very good thing.

The users have responded by adoption of new services with a higher level of trust.

Before Cloud Solutions we just assumed new services will be flaky and given time they will &quot;Get Up To Speed&quot;.

This feedback IMHO drives the Cloud and is why start ups are doing so well this this new technology.

Edward M. Goldberg</description>
		<content:encoded><![CDATA[<p>I enjoyed this post,  your point that the Developer Facing effect are the important ones IMHO misses a very important issue.</p>
<p>Success.</p>
<p>For Cloud Deployments the best feedback for the growth of the idea continues to be that it works.  Time to market is a very key feature that we tend omit talking about.</p>
<p>What the users see is applications sooner that stay working under loads that vary wildly over time.  This is a very good thing.</p>
<p>The users have responded by adoption of new services with a higher level of trust.</p>
<p>Before Cloud Solutions we just assumed new services will be flaky and given time they will &#8220;Get Up To Speed&#8221;.</p>
<p>This feedback IMHO drives the Cloud and is why start ups are doing so well this this new technology.</p>
<p>Edward M. Goldberg</p>
]]></content:encoded>
	</item>
</channel>
</rss>
