<?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: Clouds Evolve: Dealing with Infrastructure Complexity</title>
	<atom:link href="http://diego.caravana.to/clouds-evolve-dealing-with-infrastructure-complexity/feed/" rel="self" type="application/rss+xml" />
	<link>http://diego.caravana.to/clouds-evolve-dealing-with-infrastructure-complexity/</link>
	<description>Simplicity - the art of maximizing the amount of work not done</description>
	<lastBuildDate>Mon, 22 Aug 2011 16:18:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Diego Caravana</title>
		<link>http://diego.caravana.to/clouds-evolve-dealing-with-infrastructure-complexity/#comment-17800</link>
		<dc:creator>Diego Caravana</dc:creator>
		<pubDate>Sat, 12 Jul 2008 15:49:50 +0000</pubDate>
		<guid isPermaLink="false">http://diego.caravana.to/?p=228#comment-17800</guid>
		<description>Thank you very much for your comment, well done! I&#039;ll take the time to respond to it with a full post because it helps me understand better what is a cloud and in which ways can be helpful and better than bare hardware/virtualization/shared hosting.
Here I want to say only that cloud computing *is* different from shared hosting, like a programming language is different from assembly or an operating system is different from hardware, because it helps humans deal better with complexity.</description>
		<content:encoded><![CDATA[<p>Thank you very much for your comment, well done! I’ll take the time to respond to it with a full post because it helps me understand better what is a cloud and in which ways can be helpful and better than bare hardware/virtualization/shared hosting.<br />
Here I want to say only that cloud computing *is* different from shared hosting, like a programming language is different from assembly or an operating system is different from hardware, because it helps humans deal better with complexity.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rauno</title>
		<link>http://diego.caravana.to/clouds-evolve-dealing-with-infrastructure-complexity/#comment-17671</link>
		<dc:creator>Rauno</dc:creator>
		<pubDate>Tue, 08 Jul 2008 15:36:00 +0000</pubDate>
		<guid isPermaLink="false">http://diego.caravana.to/?p=228#comment-17671</guid>
		<description>Why I&#039;m against cloud?

There was a time when people was drive to buy hosting solution, and the one that had few money got &#039;shared hosting&#039; solutions. To have a &#039;shared hosting&#039; was something bad, poor performance, unknown infrastructure details, high dependency on hosting provider commercial and technical policies to guarantee the level of services. But one day some marketing guy had a very smart idea. He took the &#039;shared hosting&#039; solution and start to refer to it as &#039;cloud services&#039;, and it become a cool solution :) ... amazing the power of marketing tools!

Beside this joke (not really a joke honestly): cloud (let&#039;s call it as it has to be called: shared hosting) is a good solution if your application is not critical.From a system engineer point of view to administer a could (as for every virtualized\consolidated environment) is a mess. It does reduce costs in terms of hardware but it mean incomparable complexity in terms of monitoring, maintenance and analysis (expecially for performance). Took this together with the commercial aspect (the same 100 G of disk space sold to 20 different customers because they will never use it completely, but when this happen? and you know that this will happen at a certain point in time). First thing that happen when you have a virtualized\consolidated environment is that you start to experience random slowness, this is usually linked to latency and conflict on I\O resources (network and more frequently disks). When your service is hosted in a cloud you will never been able to discover where the bottleneck is and you will keep your random slowness after month and month of code review to try to identify the issue internally to the application.

Shared hosting is good for non critical application (my personal web site is proudly on a shared hosting but I really do not care if it remains unavailable even for days and performance is really far far to be a concern for it) but critical application do require dedicated services, where it is possible to control the resource available and used (and for the same reason in most cases also a dedicated virtual platform is not enough but physical machines are required). 

Ciao

Rauno</description>
		<content:encoded><![CDATA[<p>Why I’m against cloud?</p>
<p>There was a time when people was drive to buy hosting solution, and the one that had few money got ‘shared hosting’ solutions. To have a ‘shared hosting’ was something bad, poor performance, unknown infrastructure details, high dependency on hosting provider commercial and technical policies to guarantee the level of services. But one day some marketing guy had a very smart idea. He took the ‘shared hosting’ solution and start to refer to it as ‘cloud services’, and it become a cool solution <img src='http://diego.caravana.to/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  … amazing the power of marketing tools!</p>
<p>Beside this joke (not really a joke honestly): cloud (let’s call it as it has to be called: shared hosting) is a good solution if your application is not critical.From a system engineer point of view to administer a could (as for every virtualized\consolidated environment) is a mess. It does reduce costs in terms of hardware but it mean incomparable complexity in terms of monitoring, maintenance and analysis (expecially for performance). Took this together with the commercial aspect (the same 100 G of disk space sold to 20 different customers because they will never use it completely, but when this happen? and you know that this will happen at a certain point in time). First thing that happen when you have a virtualized\consolidated environment is that you start to experience random slowness, this is usually linked to latency and conflict on I\O resources (network and more frequently disks). When your service is hosted in a cloud you will never been able to discover where the bottleneck is and you will keep your random slowness after month and month of code review to try to identify the issue internally to the application.</p>
<p>Shared hosting is good for non critical application (my personal web site is proudly on a shared hosting but I really do not care if it remains unavailable even for days and performance is really far far to be a concern for it) but critical application do require dedicated services, where it is possible to control the resource available and used (and for the same reason in most cases also a dedicated virtual platform is not enough but physical machines are required). </p>
<p>Ciao</p>
<p>Rauno</p>
]]></content:encoded>
	</item>
</channel>
</rss>

