<?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/"
		>
<channel>
	<title>Comments on: Is cloud computing stable in bad weather?</title>
	<atom:link href="http://www.bitcurrent.com/is-cloud-computing-stable-in-bad-weather/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bitcurrent.com/is-cloud-computing-stable-in-bad-weather/</link>
	<description>Just another WordPress site</description>
	<lastBuildDate>Mon, 21 Nov 2011 22:52:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Ian Rae</title>
		<link>http://www.bitcurrent.com/is-cloud-computing-stable-in-bad-weather/#comment-540</link>
		<dc:creator>Ian Rae</dc:creator>
		<pubDate>Wed, 26 Nov 2008 22:22:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitcurrent.com/?p=329#comment-540</guid>
		<description>My principal point was that network effects could affect large, relatively open clouds. This wasn&#039;t intended to burst any bubbles as I&#039;m a huge fan of cloud computing and both my business and customers rely heavily on it! Rather this post is an observation that the behavior of complex and interconnected systems is at odds with predictable performance, availability and scalability.

To switch to the &quot;private cloud&quot; question, this may a semantic disagreement, but I also believe that such on-demand utility computing is as useful in the enterprise data center as on the public &quot;internets.&quot; Hence the concept of a private cloud where I have my physical resources dedicated to a specially authorized group of users (i.e. my customers, who have some requirements not met by AWS) with a much more tightly controlled cloud architecture, allowing on demand computing, pay-per-use billing to various departments, granular SLA monitoring, etc..

As previously written here, we will likely see different cloud computing ecosystems, with vertically targeted clouds (i.e. &quot;genome analysis cloud&quot; or a HIPAA cloud) that are architected for specific workloads. And I think some will require private control (data sensitivity...or SLA requirements etc..) while benefiting from the same flexible technology as public clouds. To think that publicly available cloud computing will solve every computing requirement would be naive.

The hybrid model of public-private cloud computing is very interesting for certain kinds of applications (www.smugmug.com did a great implementation here from what I understand) but not very practical for most at this point. Certainly one of the top requests I get from customers these days is how to take advantage of the &quot;promise&quot; of virtually unlimited scalability, so they don&#039;t have to over-provision internally. Its a nice theory but the world get real very fast when you set about running things this way.</description>
		<content:encoded><![CDATA[<p>My principal point was that network effects could affect large, relatively open clouds. This wasn&#8217;t intended to burst any bubbles as I&#8217;m a huge fan of cloud computing and both my business and customers rely heavily on it! Rather this post is an observation that the behavior of complex and interconnected systems is at odds with predictable performance, availability and scalability.</p>
<p>To switch to the &#8220;private cloud&#8221; question, this may a semantic disagreement, but I also believe that such on-demand utility computing is as useful in the enterprise data center as on the public &#8220;internets.&#8221; Hence the concept of a private cloud where I have my physical resources dedicated to a specially authorized group of users (i.e. my customers, who have some requirements not met by AWS) with a much more tightly controlled cloud architecture, allowing on demand computing, pay-per-use billing to various departments, granular SLA monitoring, etc..</p>
<p>As previously written here, we will likely see different cloud computing ecosystems, with vertically targeted clouds (i.e. &#8220;genome analysis cloud&#8221; or a HIPAA cloud) that are architected for specific workloads. And I think some will require private control (data sensitivity&#8230;or SLA requirements etc..) while benefiting from the same flexible technology as public clouds. To think that publicly available cloud computing will solve every computing requirement would be naive.</p>
<p>The hybrid model of public-private cloud computing is very interesting for certain kinds of applications (www.smugmug.com did a great implementation here from what I understand) but not very practical for most at this point. Certainly one of the top requests I get from customers these days is how to take advantage of the &#8220;promise&#8221; of virtually unlimited scalability, so they don&#8217;t have to over-provision internally. Its a nice theory but the world get real very fast when you set about running things this way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reuven Cohen, CTO Enomaly Inc</title>
		<link>http://www.bitcurrent.com/is-cloud-computing-stable-in-bad-weather/#comment-539</link>
		<dc:creator>Reuven Cohen, CTO Enomaly Inc</dc:creator>
		<pubDate>Wed, 26 Nov 2008 17:05:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.bitcurrent.com/?p=329#comment-539</guid>
		<description>ian, your post reads like the doom and gloom forecasts we saw about cloud computing back in 2007. Cloud computing is as much about trust as it is about efficiency.  The real question you should be asking is do I trust microsoft, amazon or even AT&amp;T to mange my infrastructure better then an internal data center team, and in my rather bias opinion the answer for the most part is yes.

Also, about your comment on outages, the question isn&#039;t will the cloud provider go down, because it certainly will. The real question is how do I enable a hybrid cloud environment that assumes failure and can do so gracefully. (This one of my main motivators for a unified cloud interface standard)

Lastly, as some one who has built a business on the so called private cloud platform. The idea of a quarantined shared internal cloud, aka private cloud is an oxymoron. Cloud computing is about using resources where ever and when ever, internally or externally.</description>
		<content:encoded><![CDATA[<p>ian, your post reads like the doom and gloom forecasts we saw about cloud computing back in 2007. Cloud computing is as much about trust as it is about efficiency.  The real question you should be asking is do I trust microsoft, amazon or even AT&amp;T to mange my infrastructure better then an internal data center team, and in my rather bias opinion the answer for the most part is yes.</p>
<p>Also, about your comment on outages, the question isn&#8217;t will the cloud provider go down, because it certainly will. The real question is how do I enable a hybrid cloud environment that assumes failure and can do so gracefully. (This one of my main motivators for a unified cloud interface standard)</p>
<p>Lastly, as some one who has built a business on the so called private cloud platform. The idea of a quarantined shared internal cloud, aka private cloud is an oxymoron. Cloud computing is about using resources where ever and when ever, internally or externally.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

