<?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: 5 Reasons Simple Cloud is a Dark Cloud</title>
	<atom:link href="http://claylo.com/5-reasons-simple-cloud-is-a-dark-cloud/feed" rel="self" type="application/rss+xml" />
	<link>http://claylo.com/5-reasons-simple-cloud-is-a-dark-cloud</link>
	<description></description>
	<lastBuildDate>Wed, 28 Oct 2009 13:09:37 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sam Hennessy</title>
		<link>http://claylo.com/5-reasons-simple-cloud-is-a-dark-cloud/comment-page-1#comment-299</link>
		<dc:creator>Sam Hennessy</dc:creator>
		<pubDate>Fri, 25 Sep 2009 20:08:59 +0000</pubDate>
		<guid isPermaLink="false">http://claylo.com/?p=80#comment-299</guid>
		<description>Disclaimer: I work for Zend, but I nothing to do with this project.

Some of the value I see from projects like Simple Cloud, would be to help alleviate the fear of vendor lock in.

While this is not as big a deal as you have pointed out, it&#039;s nice to have the tools that you can take to a decision maker to allow you to more easily get buy in. 

In the end, projects like this may not be of value to everyone, but they will drive the cloud forward and I think that&#039;s a positive thing.</description>
		<content:encoded><![CDATA[<p>Disclaimer: I work for Zend, but I nothing to do with this project.</p>
<p>Some of the value I see from projects like Simple Cloud, would be to help alleviate the fear of vendor lock in.</p>
<p>While this is not as big a deal as you have pointed out, it&#8217;s nice to have the tools that you can take to a decision maker to allow you to more easily get buy in. </p>
<p>In the end, projects like this may not be of value to everyone, but they will drive the cloud forward and I think that&#8217;s a positive thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wil Sinclair</title>
		<link>http://claylo.com/5-reasons-simple-cloud-is-a-dark-cloud/comment-page-1#comment-298</link>
		<dc:creator>Wil Sinclair</dc:creator>
		<pubDate>Fri, 25 Sep 2009 17:36:37 +0000</pubDate>
		<guid isPermaLink="false">http://claylo.com/?p=80#comment-298</guid>
		<description>Hi, Clay. As the guy who&#039;s mostly responsible for the API, I&#039;m probably the best person at the moment to respond to the great points you make.

1) The DB abstraction analogy is very appropriate in many ways, but IMO you take it pretty far without tying it back to the API. Yes, there will be what we call &#039;vendor value add&#039; features that more advanced cloud applications are likely to use. We&#039;ve openly embraced this fact. We offer access to the basic functionality with the Simple Cloud API, and we have the luxury of having full-featured client libs that developers can drop down to in ZF. So, why use the API if you plan to use such features? For one, you will have a much clearer distinction between value-add features and common features so that you know when you&#039;re locking in and can more easily migrate if you must. Also, you will also have only one very simple and stable API to learn, even if you switch vendors. The Simple Cloud API is also *extremely* thin to the point that it adds negligible overhead to the calls made by the client libs in ZF. There is no magic under the hood, and no generation of anything, so I&#039;m not sure what the complex SQL generation has to do with anything here to be honest.

2) See 1)

3) Keep in mind that Amazon hasn&#039;t said no yet. :) In fact, we have an ongoing discussion with them, and they are very interested in what we&#039;re doing both in the API and the AWS client libs in ZF. But regardless of whether they contribute to the Simple Cloud API, the adapters for their services are still full featured due to community and Zend&#039;s own contributions. While Amazon will always be welcome to join the effort- along with any other cloud player that can contribute- we recognize that they are the leader in the cloud space and have therefore ensured we support them well. I also personally believe that MS, Rackspace, Nirvanix, and GoGrid are true leaders in their cloud offerings, and IBM is leading thought around cloud technologies. I also think IBM will have a great impact and influence on the cloud space if/when they release their own offerings.

4) Well, adoption of the Simple Cloud API isn&#039;t hard either. :) And there are still benefits even if you don&#039;t switch (see 1)). 

5) True, established apps may never switch. But developers evaluating services for their barely written apps (likely nothing more than prototypes) are likely to switch around until they find the right platform for them. After they&#039;ve found the right service they&#039;ll see no reason to move off of the Simple Cloud API if we&#039;ve met our goals with the project. And keep in mind that not all cloud apps have the cloud requirements that your apps have. :)

In any case, thanks for the feedback. I&#039;d really appreciate it if you started a forum topic about this here: http://www.simplecloud.org/forum. And/or dicuss this with me in an open forum like a webinar, etc.

Thanks again!
,Wil</description>
		<content:encoded><![CDATA[<p>Hi, Clay. As the guy who&#8217;s mostly responsible for the API, I&#8217;m probably the best person at the moment to respond to the great points you make.</p>
<p>1) The DB abstraction analogy is very appropriate in many ways, but IMO you take it pretty far without tying it back to the API. Yes, there will be what we call &#8216;vendor value add&#8217; features that more advanced cloud applications are likely to use. We&#8217;ve openly embraced this fact. We offer access to the basic functionality with the Simple Cloud API, and we have the luxury of having full-featured client libs that developers can drop down to in ZF. So, why use the API if you plan to use such features? For one, you will have a much clearer distinction between value-add features and common features so that you know when you&#8217;re locking in and can more easily migrate if you must. Also, you will also have only one very simple and stable API to learn, even if you switch vendors. The Simple Cloud API is also *extremely* thin to the point that it adds negligible overhead to the calls made by the client libs in ZF. There is no magic under the hood, and no generation of anything, so I&#8217;m not sure what the complex SQL generation has to do with anything here to be honest.</p>
<p>2) See 1)</p>
<p>3) Keep in mind that Amazon hasn&#8217;t said no yet. <img src='http://claylo.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  In fact, we have an ongoing discussion with them, and they are very interested in what we&#8217;re doing both in the API and the AWS client libs in ZF. But regardless of whether they contribute to the Simple Cloud API, the adapters for their services are still full featured due to community and Zend&#8217;s own contributions. While Amazon will always be welcome to join the effort- along with any other cloud player that can contribute- we recognize that they are the leader in the cloud space and have therefore ensured we support them well. I also personally believe that MS, Rackspace, Nirvanix, and GoGrid are true leaders in their cloud offerings, and IBM is leading thought around cloud technologies. I also think IBM will have a great impact and influence on the cloud space if/when they release their own offerings.</p>
<p>4) Well, adoption of the Simple Cloud API isn&#8217;t hard either. <img src='http://claylo.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />  And there are still benefits even if you don&#8217;t switch (see 1)). </p>
<p>5) True, established apps may never switch. But developers evaluating services for their barely written apps (likely nothing more than prototypes) are likely to switch around until they find the right platform for them. After they&#8217;ve found the right service they&#8217;ll see no reason to move off of the Simple Cloud API if we&#8217;ve met our goals with the project. And keep in mind that not all cloud apps have the cloud requirements that your apps have. <img src='http://claylo.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>In any case, thanks for the feedback. I&#8217;d really appreciate it if you started a forum topic about this here: <a href="http://www.simplecloud.org/forum" rel="nofollow">http://www.simplecloud.org/forum</a>. And/or dicuss this with me in an open forum like a webinar, etc.</p>
<p>Thanks again!<br />
,Wil</p>
]]></content:encoded>
	</item>
</channel>
</rss>
