<?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: Amazon Web Services or Joyent Accelerators: Reprise</title>
	<atom:link href="http://joyeur.com/2008/05/15/amazon-web-services-or-joyent-accelerators-reprise/feed/" rel="self" type="application/rss+xml" />
	<link>http://joyeur.com/2008/05/15/amazon-web-services-or-joyent-accelerators-reprise/</link>
	<description>Joyent&#039;s Weblog</description>
	<lastBuildDate>Sat, 11 Feb 2012 02:02:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Ivo</title>
		<link>http://joyeur.com/2008/05/15/amazon-web-services-or-joyent-accelerators-reprise/#comment-3258</link>
		<dc:creator><![CDATA[Ivo]]></dc:creator>
		<pubDate>Mon, 26 May 2008 18:25:49 +0000</pubDate>
		<guid isPermaLink="false">http://joycomad.joyent.us/blog/uncategorized/amazon-web-services-or-joyent-accelerators-reprise/#comment-3258</guid>
		<description><![CDATA[And there&#8217;s OpenSolaris on EC2 as well:

	http://blogs.sun.com/ec2/entry/launch_of_opensolaris_on_amazon]]></description>
		<content:encoded><![CDATA[<p>And there&#8217;s OpenSolaris on EC2 as well:</p>
<p>	<a href="http://blogs.sun.com/ec2/entry/launch_of_opensolaris_on_amazon" rel="nofollow">http://blogs.sun.com/ec2/entry/launch_of_opensolaris_on_amazon</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vince</title>
		<link>http://joyeur.com/2008/05/15/amazon-web-services-or-joyent-accelerators-reprise/#comment-3199</link>
		<dc:creator><![CDATA[Vince]]></dc:creator>
		<pubDate>Mon, 19 May 2008 17:31:56 +0000</pubDate>
		<guid isPermaLink="false">http://joycomad.joyent.us/blog/uncategorized/amazon-web-services-or-joyent-accelerators-reprise/#comment-3199</guid>
		<description><![CDATA[@Dom

	In case you weren&#8217;t aware, Amazon does provide paid support (Silver &amp; Gold) &#8211; much like Joyent does for it&#8217;s Accelerators.

	See the link below

	http://www.amazon.com/gp/browse.html?node=566801011]]></description>
		<content:encoded><![CDATA[<p>@Dom</p>
<p>	In case you weren&#8217;t aware, Amazon does provide paid support (Silver &amp; Gold) &#8211; much like Joyent does for it&#8217;s Accelerators.</p>
<p>	See the link below</p>
<p>	<a href="http://www.amazon.com/gp/browse.html?node=566801011" rel="nofollow">http://www.amazon.com/gp/browse.html?node=566801011</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dom</title>
		<link>http://joyeur.com/2008/05/15/amazon-web-services-or-joyent-accelerators-reprise/#comment-3198</link>
		<dc:creator><![CDATA[Dom]]></dc:creator>
		<pubDate>Mon, 19 May 2008 16:49:29 +0000</pubDate>
		<guid isPermaLink="false">http://joycomad.joyent.us/blog/uncategorized/amazon-web-services-or-joyent-accelerators-reprise/#comment-3198</guid>
		<description><![CDATA[I have to admit I was seduced by AWS only a few weeks ago. I used a prominent service to build my virtual server image and experienced the fastest and most flawless deployment of any software ever. The low cost and fast build and deployment time, and knowing I&#8217;d only be billed for actual usage as opposed to paying upfront for bandwidth and disk space I might not necessarily use, was enthralling.

	But my party soon ended. With no support and little experience in the linux world, I&#8217;ve been driven back to a hosted solution.

	The good news &#8211; I found Joyent.]]></description>
		<content:encoded><![CDATA[<p>I have to admit I was seduced by AWS only a few weeks ago. I used a prominent service to build my virtual server image and experienced the fastest and most flawless deployment of any software ever. The low cost and fast build and deployment time, and knowing I&#8217;d only be billed for actual usage as opposed to paying upfront for bandwidth and disk space I might not necessarily use, was enthralling.</p>
<p>	But my party soon ended. With no support and little experience in the linux world, I&#8217;ve been driven back to a hosted solution.</p>
<p>	The good news &#8211; I found Joyent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seth</title>
		<link>http://joyeur.com/2008/05/15/amazon-web-services-or-joyent-accelerators-reprise/#comment-3197</link>
		<dc:creator><![CDATA[Seth]]></dc:creator>
		<pubDate>Sat, 17 May 2008 10:40:32 +0000</pubDate>
		<guid isPermaLink="false">http://joycomad.joyent.us/blog/uncategorized/amazon-web-services-or-joyent-accelerators-reprise/#comment-3197</guid>
		<description><![CDATA[Amazon has a very simple advantage, you pay for what you use. I can scale instantly and I can deploy servers as needed. I agree the basic 3 tier web deployment doesn&#8217;t work for high traffic sites, but for smaller startups it works fine.

	No hardware load balancer, but I can setup a high availability deployment across different datacenters aka &#8220;Availability Zones&#8221;. That&#8217;s not something many cloud providers will be able to offer.

	If the box where your load balancer lives dies, relaunch the instance and your are back online.

	With the Joyent Accelerators, is there a cancellation process for each instance I might not need ? With Amazon I can simple terminate the instance and I&#8217;m done.

	This is a perfect example of what you need to be able to do with cloud computing.
http://blog.animoto.com/2008/04/21/amazon-ceo-jeff-bezos-on-animoto/]]></description>
		<content:encoded><![CDATA[<p>Amazon has a very simple advantage, you pay for what you use. I can scale instantly and I can deploy servers as needed. I agree the basic 3 tier web deployment doesn&#8217;t work for high traffic sites, but for smaller startups it works fine.</p>
<p>	No hardware load balancer, but I can setup a high availability deployment across different datacenters aka &#8220;Availability Zones&#8221;. That&#8217;s not something many cloud providers will be able to offer.</p>
<p>	If the box where your load balancer lives dies, relaunch the instance and your are back online.</p>
<p>	With the Joyent Accelerators, is there a cancellation process for each instance I might not need ? With Amazon I can simple terminate the instance and I&#8217;m done.</p>
<p>	This is a perfect example of what you need to be able to do with cloud computing.<br />
<a href="http://blog.animoto.com/2008/04/21/amazon-ceo-jeff-bezos-on-animoto/" rel="nofollow">http://blog.animoto.com/2008/04/21/amazon-ceo-jeff-bezos-on-animoto/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Young</title>
		<link>http://joyeur.com/2008/05/15/amazon-web-services-or-joyent-accelerators-reprise/#comment-3196</link>
		<dc:creator><![CDATA[David Young]]></dc:creator>
		<pubDate>Sat, 17 May 2008 02:54:11 +0000</pubDate>
		<guid isPermaLink="false">http://joycomad.joyent.us/blog/uncategorized/amazon-web-services-or-joyent-accelerators-reprise/#comment-3196</guid>
		<description><![CDATA[@Teddy: Joyent has an API. Aptana is using it to deliver cloud computing services to their customers. Neither Joyent nor Amazon have state layer interoperability. Neither Joyent nor Amazon have automatic scale. That&#8217;s why I gave Joyent a 7. Without hardware load-balancing, I&#8217;d give Amazon a 6 cloud score.

	Beyond the scoring, do you agree with the nine traits of a cloud computer?]]></description>
		<content:encoded><![CDATA[<p>@Teddy: Joyent has an API. Aptana is using it to deliver cloud computing services to their customers. Neither Joyent nor Amazon have state layer interoperability. Neither Joyent nor Amazon have automatic scale. That&#8217;s why I gave Joyent a 7. Without hardware load-balancing, I&#8217;d give Amazon a 6 cloud score.</p>
<p>	Beyond the scoring, do you agree with the nine traits of a cloud computer?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Teddy K</title>
		<link>http://joyeur.com/2008/05/15/amazon-web-services-or-joyent-accelerators-reprise/#comment-3195</link>
		<dc:creator><![CDATA[Teddy K]]></dc:creator>
		<pubDate>Fri, 16 May 2008 23:25:59 +0000</pubDate>
		<guid isPermaLink="false">http://joycomad.joyent.us/blog/uncategorized/amazon-web-services-or-joyent-accelerators-reprise/#comment-3195</guid>
		<description><![CDATA[Since you guys just wrote the other day a blog post that establishes a metric of 9 traits for cloud computing, let&#8217;s compare Joyent to Amazon.

	http://www.joyeur.com/2008/05/08/cloud-nine-specification-for-a-cloud-computer-a-call-to-action

	1) Virtualization Layer Network Stability
Joyent = Yes, Amazon = Yes

	2) API for Creation, Deletion, Cloning of Instances
Joyent = No, Amazon = Yes

	3) Application Layer Interoperability
Joyent = Yes, Amazon = Yes

	4) State Layer Interoperability (most difficult)
Joyent = No, Amazon = Yes

	5) Application Services (e.g. email infrastructure, payments infrastructure)
Joyent = Yes, Amazon = Yes

	6) Automatic Scale (deploy and forget about it)
Joyent = No, Amazon = Yes

	7) Hardware Load Balancing
Joyent = Yes, Amazon = No

	8) Storage as a Service
Joyent = Yes, Amazon = Yes

	9) “Root”, If Required
Joyent = Yes, Amazon = Yes

	&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;

	Totals:  Joyent 6/9, Amazon 8/9]]></description>
		<content:encoded><![CDATA[<p>Since you guys just wrote the other day a blog post that establishes a metric of 9 traits for cloud computing, let&#8217;s compare Joyent to Amazon.</p>
<p>	<a href="http://www.joyeur.com/2008/05/08/cloud-nine-specification-for-a-cloud-computer-a-call-to-action" rel="nofollow">http://www.joyeur.com/2008/05/08/cloud-nine-specification-for-a-cloud-computer-a-call-to-action</a></p>
<p>	1) Virtualization Layer Network Stability<br />
Joyent = Yes, Amazon = Yes</p>
<p>	2) API for Creation, Deletion, Cloning of Instances<br />
Joyent = No, Amazon = Yes</p>
<p>	3) Application Layer Interoperability<br />
Joyent = Yes, Amazon = Yes</p>
<p>	4) State Layer Interoperability (most difficult)<br />
Joyent = No, Amazon = Yes</p>
<p>	5) Application Services (e.g. email infrastructure, payments infrastructure)<br />
Joyent = Yes, Amazon = Yes</p>
<p>	6) Automatic Scale (deploy and forget about it)<br />
Joyent = No, Amazon = Yes</p>
<p>	7) Hardware Load Balancing<br />
Joyent = Yes, Amazon = No</p>
<p>	8) Storage as a Service<br />
Joyent = Yes, Amazon = Yes</p>
<p>	9) “Root”, If Required<br />
Joyent = Yes, Amazon = Yes</p>
<p>	&#8212;&#8212;&#8212;&#8212;&#8212;&#8212;</p>
<p>	Totals:  Joyent 6/9, Amazon 8/9</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ramin</title>
		<link>http://joyeur.com/2008/05/15/amazon-web-services-or-joyent-accelerators-reprise/#comment-3194</link>
		<dc:creator><![CDATA[Ramin]]></dc:creator>
		<pubDate>Fri, 16 May 2008 04:48:14 +0000</pubDate>
		<guid isPermaLink="false">http://joycomad.joyent.us/blog/uncategorized/amazon-web-services-or-joyent-accelerators-reprise/#comment-3194</guid>
		<description><![CDATA[Here&#8217;s an exercise:

	- Take a single application from scratch. Something with a database,  some sort of web service interface, and an AJAX or Flex/widget interface. Not a toy, but something reasonable. 

	- Now build and deploy it on Google AppEngine, Amazon EC2/S3, and Joyent accelerator.

	- Keep meticulous note of how long it took to write, test, and debug, and more importantly, what steps were taken to deploy the app.

	- Also keep track of how much each of them cost to deploy and some on-going cost/performance scenarios.

	- Put them side-by-side.

	Whoever has the fewest number of steps and the fastest build/deploy time is likely to attract the most developers. Whoever can show that the operating cost scales linearly with use will have developers casting flower petals in their path :-)

	A few years ago there was a geek humor piece making the rounds. Someone had tried writing the &#8216;Hello World&#8217; app across a number of languages/platforms. The C and Java version were two lines. The OLE one was 3-4 pages long. It was a joke, but it reinforced the perception that OLE was hard to use and it never took off.

	As an app developer, I don&#8217;t care that it runs on Solaris, FreeBSD, or Mac-OS. I want it to work. I want an optimized deployment workflow and a simple way to monitor and keep things running.

	If you guys present a way for developers to build and deploy apps quickly and easily and keep them running cost-effectively, you&#8217;ll have to beat people off with a stick.

	Just my $0.02.]]></description>
		<content:encoded><![CDATA[<p>Here&#8217;s an exercise:</p>
<p>	- Take a single application from scratch. Something with a database,  some sort of web service interface, and an AJAX or Flex/widget interface. Not a toy, but something reasonable. </p>
<p>	- Now build and deploy it on Google AppEngine, Amazon EC2/S3, and Joyent accelerator.</p>
<p>	- Keep meticulous note of how long it took to write, test, and debug, and more importantly, what steps were taken to deploy the app.</p>
<p>	- Also keep track of how much each of them cost to deploy and some on-going cost/performance scenarios.</p>
<p>	- Put them side-by-side.</p>
<p>	Whoever has the fewest number of steps and the fastest build/deploy time is likely to attract the most developers. Whoever can show that the operating cost scales linearly with use will have developers casting flower petals in their path <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>	A few years ago there was a geek humor piece making the rounds. Someone had tried writing the &#8216;Hello World&#8217; app across a number of languages/platforms. The C and Java version were two lines. The OLE one was 3-4 pages long. It was a joke, but it reinforced the perception that OLE was hard to use and it never took off.</p>
<p>	As an app developer, I don&#8217;t care that it runs on Solaris, FreeBSD, or Mac-OS. I want it to work. I want an optimized deployment workflow and a simple way to monitor and keep things running.</p>
<p>	If you guys present a way for developers to build and deploy apps quickly and easily and keep them running cost-effectively, you&#8217;ll have to beat people off with a stick.</p>
<p>	Just my $0.02.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brendan</title>
		<link>http://joyeur.com/2008/05/15/amazon-web-services-or-joyent-accelerators-reprise/#comment-3193</link>
		<dc:creator><![CDATA[Brendan]]></dc:creator>
		<pubDate>Fri, 16 May 2008 04:29:01 +0000</pubDate>
		<guid isPermaLink="false">http://joycomad.joyent.us/blog/uncategorized/amazon-web-services-or-joyent-accelerators-reprise/#comment-3193</guid>
		<description><![CDATA[An interesting read, but I am not entirely convinced you are comparing Apples with Apples. One could argue that EC2, S3 et all are built on similarly scalable hardware and operating systems &#8211; functionality exposed to the end user is as much a choice of what makes commercial sense, as it is capabilities.

	Joyent accelerators do compare well, but their strength comes from what they run on. Fundamentally, OS choice does matter &#8211; otherwise you wouldn&#8217;t pimp Open Solaris half so much. :)

	The choice between an almost &#8216;instant on&#8217; environment, versus one that requires some effort to construct really shouldn&#8217;t be dismissed too lightly. So it&#8217;s more a comparison between an operating system (which is really the core point here, given the discourse on kernels and hypervisors) and Amazon&#8217;s actual application framework, rather than what it actually runs on.]]></description>
		<content:encoded><![CDATA[<p>An interesting read, but I am not entirely convinced you are comparing Apples with Apples. One could argue that EC2, S3 et all are built on similarly scalable hardware and operating systems &#8211; functionality exposed to the end user is as much a choice of what makes commercial sense, as it is capabilities.</p>
<p>	Joyent accelerators do compare well, but their strength comes from what they run on. Fundamentally, OS choice does matter &#8211; otherwise you wouldn&#8217;t pimp Open Solaris half so much. <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>	The choice between an almost &#8216;instant on&#8217; environment, versus one that requires some effort to construct really shouldn&#8217;t be dismissed too lightly. So it&#8217;s more a comparison between an operating system (which is really the core point here, given the discourse on kernels and hypervisors) and Amazon&#8217;s actual application framework, rather than what it actually runs on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel Howard</title>
		<link>http://joyeur.com/2008/05/15/amazon-web-services-or-joyent-accelerators-reprise/#comment-3192</link>
		<dc:creator><![CDATA[Daniel Howard]]></dc:creator>
		<pubDate>Fri, 16 May 2008 04:00:58 +0000</pubDate>
		<guid isPermaLink="false">http://joycomad.joyent.us/blog/uncategorized/amazon-web-services-or-joyent-accelerators-reprise/#comment-3192</guid>
		<description><![CDATA[Hi,

	I agree the Joyent Accelerator compares favorably with Amazon&#8217;s offering.  For me, though, the big win for Amazon is that I can deploy server instances in minutes, whereas my reading of Joyent&#8217;s offering was that provisioning an accelerator costs $50 and can take a few days.  Amazon&#8217;s initial barrier to adoption is really low, and that is going to draw a developer in to start playing quick and cheap.  It would be neat if Joyent could provide faster, cheaper turnaround on new services.

	Sincerely,
-daniel]]></description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>	I agree the Joyent Accelerator compares favorably with Amazon&#8217;s offering.  For me, though, the big win for Amazon is that I can deploy server instances in minutes, whereas my reading of Joyent&#8217;s offering was that provisioning an accelerator costs $50 and can take a few days.  Amazon&#8217;s initial barrier to adoption is really low, and that is going to draw a developer in to start playing quick and cheap.  It would be neat if Joyent could provide faster, cheaper turnaround on new services.</p>
<p>	Sincerely,<br />
-daniel</p>
]]></content:encoded>
	</item>
</channel>
</rss>

