<?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: Cost of cloud computing, expensive!</title>
	<atom:link href="http://www.uptimesoftware.com/uptimeblog/cloud-virtualization/cost-of-cloud-computing-expensive/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uptimesoftware.com/uptimeblog/cloud-virtualization/cost-of-cloud-computing-expensive/</link>
	<description></description>
	<lastBuildDate>Fri, 12 Mar 2010 14:57:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Johnny</title>
		<link>http://www.uptimesoftware.com/uptimeblog/cloud-virtualization/cost-of-cloud-computing-expensive/comment-page-1/#comment-152</link>
		<dc:creator>Johnny</dc:creator>
		<pubDate>Fri, 22 Jan 2010 15:43:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.uptimesoftware.com/uptimeblog/2009/01/cost-of-cloud-computing-expensive/#comment-152</guid>
		<description>Your information has really proven to be helpful. Thanks allot. Oh and in regards to the post by Bruce. I totally agree with you on that. The cost of implementing and licensing can be astronomical.</description>
		<content:encoded><![CDATA[<p>Your information has really proven to be helpful. Thanks allot. Oh and in regards to the post by Bruce. I totally agree with you on that. The cost of implementing and licensing can be astronomical.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: 2010 &#8211; The Year of Cloud Experimentation &#8211; Part 1 of 2 &#171; The up.time IT Systems Management Blog</title>
		<link>http://www.uptimesoftware.com/uptimeblog/cloud-virtualization/cost-of-cloud-computing-expensive/comment-page-1/#comment-116</link>
		<dc:creator>2010 &#8211; The Year of Cloud Experimentation &#8211; Part 1 of 2 &#171; The up.time IT Systems Management Blog</dc:creator>
		<pubDate>Mon, 30 Nov 2009 13:42:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.uptimesoftware.com/uptimeblog/2009/01/cost-of-cloud-computing-expensive/#comment-116</guid>
		<description>[...] but feel it still has some distance to cover before it lives up to the hype. In fact, I wrote a blog in January looking at a hypothetical company and the costs involved in moving an entire [...]</description>
		<content:encoded><![CDATA[<p>[...] but feel it still has some distance to cover before it lives up to the hype. In fact, I wrote a blog in January looking at a hypothetical company and the costs involved in moving an entire [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce</title>
		<link>http://www.uptimesoftware.com/uptimeblog/cloud-virtualization/cost-of-cloud-computing-expensive/comment-page-1/#comment-105</link>
		<dc:creator>Bruce</dc:creator>
		<pubDate>Fri, 20 Nov 2009 06:39:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.uptimesoftware.com/uptimeblog/2009/01/cost-of-cloud-computing-expensive/#comment-105</guid>
		<description>Can someone explain to me something that seems obvious? Why would anyone pay such a high price for Amazon&#039;s SQL instance instead of taking a regular Windows instance and installing your own licensed version of SQL on it?</description>
		<content:encoded><![CDATA[<p>Can someone explain to me something that seems obvious? Why would anyone pay such a high price for Amazon&#8217;s SQL instance instead of taking a regular Windows instance and installing your own licensed version of SQL on it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Altax</title>
		<link>http://www.uptimesoftware.com/uptimeblog/cloud-virtualization/cost-of-cloud-computing-expensive/comment-page-1/#comment-97</link>
		<dc:creator>Altax</dc:creator>
		<pubDate>Thu, 15 Oct 2009 12:33:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.uptimesoftware.com/uptimeblog/2009/01/cost-of-cloud-computing-expensive/#comment-97</guid>
		<description>Thanks for the useful and informative post. I really like the way of your presentation.</description>
		<content:encoded><![CDATA[<p>Thanks for the useful and informative post. I really like the way of your presentation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Hodapp</title>
		<link>http://www.uptimesoftware.com/uptimeblog/cloud-virtualization/cost-of-cloud-computing-expensive/comment-page-1/#comment-75</link>
		<dc:creator>Mark Hodapp</dc:creator>
		<pubDate>Fri, 10 Jul 2009 13:26:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.uptimesoftware.com/uptimeblog/2009/01/cost-of-cloud-computing-expensive/#comment-75</guid>
		<description>Thank you for publishing your analysis.  I&#039;ve posted a response at my blog http://cloudsavvy.blogspot.com/ 

Regards,

Mark</description>
		<content:encoded><![CDATA[<p>Thank you for publishing your analysis.  I&#8217;ve posted a response at my blog <a href="http://cloudsavvy.blogspot.com/" rel="nofollow">http://cloudsavvy.blogspot.com/</a> </p>
<p>Regards,</p>
<p>Mark</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J Singh</title>
		<link>http://www.uptimesoftware.com/uptimeblog/cloud-virtualization/cost-of-cloud-computing-expensive/comment-page-1/#comment-71</link>
		<dc:creator>J Singh</dc:creator>
		<pubDate>Thu, 09 Jul 2009 17:12:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.uptimesoftware.com/uptimeblog/2009/01/cost-of-cloud-computing-expensive/#comment-71</guid>
		<description>Sorry, that is $500/(3 yrs).</description>
		<content:encoded><![CDATA[<p>Sorry, that is $500/(3 yrs).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J Singh</title>
		<link>http://www.uptimesoftware.com/uptimeblog/cloud-virtualization/cost-of-cloud-computing-expensive/comment-page-1/#comment-70</link>
		<dc:creator>J Singh</dc:creator>
		<pubDate>Thu, 09 Jul 2009 17:11:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.uptimesoftware.com/uptimeblog/2009/01/cost-of-cloud-computing-expensive/#comment-70</guid>
		<description>Apples and Oranges, IMHO.

The proper comparison would be Amazon Reserved Instances vs. purchased hardware. Reserved Instances for the type of machine you assumed go for $500/yr plus 3c/hr, as opposed to the 12.5c/hr you assumed.

There is the question of capital expenses vs. operating expenses, which could make the difference between being able to fund a program or not.

There is the factor Ron mentions above: that data centers just suck money with backup generators and cooling, physical security, internet security, etc.</description>
		<content:encoded><![CDATA[<p>Apples and Oranges, IMHO.</p>
<p>The proper comparison would be Amazon Reserved Instances vs. purchased hardware. Reserved Instances for the type of machine you assumed go for $500/yr plus 3c/hr, as opposed to the 12.5c/hr you assumed.</p>
<p>There is the question of capital expenses vs. operating expenses, which could make the difference between being able to fund a program or not.</p>
<p>There is the factor Ron mentions above: that data centers just suck money with backup generators and cooling, physical security, internet security, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chance</title>
		<link>http://www.uptimesoftware.com/uptimeblog/cloud-virtualization/cost-of-cloud-computing-expensive/comment-page-1/#comment-69</link>
		<dc:creator>Chance</dc:creator>
		<pubDate>Thu, 09 Jul 2009 14:21:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.uptimesoftware.com/uptimeblog/2009/01/cost-of-cloud-computing-expensive/#comment-69</guid>
		<description>Love the posting. There is definitely a &quot;Microsoft Tax&quot; at work when you us SQL Server. Paying over $300,000/year for a database server is just crazy! I think the best approach is for all designs/deployments of systems should look at a cost analysis like this to see if the design makes sense. Obviously the choice of SQL Server comes with some heavy costs!</description>
		<content:encoded><![CDATA[<p>Love the posting. There is definitely a &#8220;Microsoft Tax&#8221; at work when you us SQL Server. Paying over $300,000/year for a database server is just crazy! I think the best approach is for all designs/deployments of systems should look at a cost analysis like this to see if the design makes sense. Obviously the choice of SQL Server comes with some heavy costs!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ron McClintic</title>
		<link>http://www.uptimesoftware.com/uptimeblog/cloud-virtualization/cost-of-cloud-computing-expensive/comment-page-1/#comment-68</link>
		<dc:creator>Ron McClintic</dc:creator>
		<pubDate>Thu, 09 Jul 2009 13:36:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.uptimesoftware.com/uptimeblog/2009/01/cost-of-cloud-computing-expensive/#comment-68</guid>
		<description>Your analysis is very incomplete. Yes, the hardware will cost more, as you are essentially buying from a reseller instead of direct. You have omitted several overhead costs that will almost always cost more in-house than in a data center. Some obvious ones are things like shared utilites, security (physical as well as IT), emergency backup power etc. etc. How about a redundant internet connection? Do you want to pay for two yourself, or share that expense with others? Do you want your own diesel generator or pay a small part of that cost? For that matter do you want to maintain and test that generator, including replacing the tank of fuel every year so it says fresh?  

When you compare sharing those costs with other data center customers verus building it just for your situation, the savings can be greater than the hardware costs. And typically you benefit by more frequent upgrades to datacenter infrastructure, as teh data center owner has to stay more current than an in house facility. The reason being he has to stay competitive in the market to keep and attract customers.

You are correct in pointing out a major savings comes from dealing with cyclical spikes in load. Even if it costs more when you use the increased resources, it is more than made up by not paying for the resources to sit idle in your facility.

As long as  you demand the same level of reliability and robustness, I would argue that the starting assumption is, renting space and resources is more economical than doing it inhouse. This not always true, but it is true much more often than CIO/CTOs want to admit. If you are willing to compromise on reliability, in house can always be cheaper.</description>
		<content:encoded><![CDATA[<p>Your analysis is very incomplete. Yes, the hardware will cost more, as you are essentially buying from a reseller instead of direct. You have omitted several overhead costs that will almost always cost more in-house than in a data center. Some obvious ones are things like shared utilites, security (physical as well as IT), emergency backup power etc. etc. How about a redundant internet connection? Do you want to pay for two yourself, or share that expense with others? Do you want your own diesel generator or pay a small part of that cost? For that matter do you want to maintain and test that generator, including replacing the tank of fuel every year so it says fresh?  </p>
<p>When you compare sharing those costs with other data center customers verus building it just for your situation, the savings can be greater than the hardware costs. And typically you benefit by more frequent upgrades to datacenter infrastructure, as teh data center owner has to stay more current than an in house facility. The reason being he has to stay competitive in the market to keep and attract customers.</p>
<p>You are correct in pointing out a major savings comes from dealing with cyclical spikes in load. Even if it costs more when you use the increased resources, it is more than made up by not paying for the resources to sit idle in your facility.</p>
<p>As long as  you demand the same level of reliability and robustness, I would argue that the starting assumption is, renting space and resources is more economical than doing it inhouse. This not always true, but it is true much more often than CIO/CTOs want to admit. If you are willing to compromise on reliability, in house can always be cheaper.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter LeBlond</title>
		<link>http://www.uptimesoftware.com/uptimeblog/cloud-virtualization/cost-of-cloud-computing-expensive/comment-page-1/#comment-14</link>
		<dc:creator>Peter LeBlond</dc:creator>
		<pubDate>Fri, 24 Apr 2009 20:09:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.uptimesoftware.com/uptimeblog/2009/01/cost-of-cloud-computing-expensive/#comment-14</guid>
		<description>I guess I don&#039;t know why you have 32 physical machines under your in-house tally and 302 instances under AWS. Can you really accomplish as much with 30 Dell boxes (28 of which are 1950s) as you can with 300 AWS instances?

I suppose if you are already highly virtualized in-house and you run a lot of VM&#039;s that aren&#039;t all that busy that your costs wouldn&#039;t translate to AWS instances which are built to be full power machines. Or did you find that the AMIs were not able to do the same workload as your in-house machines?

Peter</description>
		<content:encoded><![CDATA[<p>I guess I don&#8217;t know why you have 32 physical machines under your in-house tally and 302 instances under AWS. Can you really accomplish as much with 30 Dell boxes (28 of which are 1950s) as you can with 300 AWS instances?</p>
<p>I suppose if you are already highly virtualized in-house and you run a lot of VM&#8217;s that aren&#8217;t all that busy that your costs wouldn&#8217;t translate to AWS instances which are built to be full power machines. Or did you find that the AMIs were not able to do the same workload as your in-house machines?</p>
<p>Peter</p>
]]></content:encoded>
	</item>
</channel>
</rss>
