<?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 RDS: Poison or Pill</title>
	<atom:link href="http://nessence.net/2009/10/29/amazon-rds-poison-or-pill/feed/" rel="self" type="application/rss+xml" />
	<link>http://nessence.net/2009/10/29/amazon-rds-poison-or-pill/</link>
	<description>Technology; until we all find something new.</description>
	<lastBuildDate>Wed, 07 Jul 2010 05:21:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Alex Leverington</title>
		<link>http://nessence.net/2009/10/29/amazon-rds-poison-or-pill/#comment-258</link>
		<dc:creator>Alex Leverington</dc:creator>
		<pubDate>Wed, 07 Jul 2010 05:21:42 +0000</pubDate>
		<guid isPermaLink="false">http://nessence.net/?p=227#comment-258</guid>
		<description>I addressed your comments in the closing of my post, as well as a cost analysis both Amazon and RDS users. Like I stated -- don&#039;t rely on RDS -- not sure if you&#039;ve kept up with the news lately but Amazon (incl RDS) has experienced failures involving data loss.

I also don&#039;t think you&#039;ve taken into account when happens when one needs to &quot;scale&quot; mysql past the confines of on server. You can add as much memory or CPU to a mysql box as you want but, in an optimal environment, the limitation will almost always disk I/O. An IT, developer, or otherwise thinking they can just &quot;move to RDS&quot; to solve their mysql scalability issues should rethink their situation -- Amazon RDS garners little gain in I/O over a dedicated server. Except for small shops, without extended support for replication or other beneficial features, there is simply no benefit to migrate to RDS over simply understanding how to properly configure and deploy mysql within your own environment.</description>
		<content:encoded><![CDATA[<p>I addressed your comments in the closing of my post, as well as a cost analysis both Amazon and RDS users. Like I stated &#8212; don&#8217;t rely on RDS &#8212; not sure if you&#8217;ve kept up with the news lately but Amazon (incl RDS) has experienced failures involving data loss.</p>
<p>I also don&#8217;t think you&#8217;ve taken into account when happens when one needs to &#8220;scale&#8221; mysql past the confines of on server. You can add as much memory or CPU to a mysql box as you want but, in an optimal environment, the limitation will almost always disk I/O. An IT, developer, or otherwise thinking they can just &#8220;move to RDS&#8221; to solve their mysql scalability issues should rethink their situation &#8212; Amazon RDS garners little gain in I/O over a dedicated server. Except for small shops, without extended support for replication or other beneficial features, there is simply no benefit to migrate to RDS over simply understanding how to properly configure and deploy mysql within your own environment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amitava Biswas</title>
		<link>http://nessence.net/2009/10/29/amazon-rds-poison-or-pill/#comment-257</link>
		<dc:creator>Amitava Biswas</dc:creator>
		<pubDate>Tue, 06 Jul 2010 22:28:44 +0000</pubDate>
		<guid isPermaLink="false">http://nessence.net/?p=227#comment-257</guid>
		<description>Well, think this point from business viewpoint. Does a MySQL analog on cloud makes it easier to port your legacy apps on the cloud and derive benefit what cloud proposes ? I think the answer is YES !

If my code are reusable (now that RDS is there), why won&#039;t I move my apps to cloud and try get rid of my IT overheads (and the headache) ? Didn&#039;t we outsource to India and China and focus on our core operations ? instead of being at the mercy of IT dept in US ? Thinks it as IT function outsourcing, while keeping the IS function in house (same as splitting design and Silicon fabrication functions in 80&#039;s in Chip business)

So from Amazon&#039;s (and all our) viewpoint it makes sense -
1) It lowers the entry barrier to users and developers to get into cloud.
2) It enables faster adoption of cloud, and thereby brings in investment to further stimulate cloud tech development (remember Ford had said -&quot;..they can have any color as they want as long as it is black...&quot; about model T, whose standardization had helped build economy of scale and helped the auto industry)

The argument against RDS would have been stronger if the above analysis had done a comparison on economics and argued from business and strategic angles, rather than speculating that my own backup would be much better than Amazon&#039;s professionally managed data centers.

Sure RDS is relational db thinking, which is not the cutting edge, but it still has its role to play (assuming the RDS is much faster that SimpleDB, else RDS and SimpleDB has to compete with each other)  Amazon should be careful against such possible internal conflict and canabalisation, and the RDS engineering team have to keep better latencies in RDS compared to SimpleDB, would be interesting to see how each team does that over next 3 years).
I am sure Amazon&#039;s executive may have thought about such Darwinian strategy to stimulate tech development internally.</description>
		<content:encoded><![CDATA[<p>Well, think this point from business viewpoint. Does a MySQL analog on cloud makes it easier to port your legacy apps on the cloud and derive benefit what cloud proposes ? I think the answer is YES !</p>
<p>If my code are reusable (now that RDS is there), why won&#8217;t I move my apps to cloud and try get rid of my IT overheads (and the headache) ? Didn&#8217;t we outsource to India and China and focus on our core operations ? instead of being at the mercy of IT dept in US ? Thinks it as IT function outsourcing, while keeping the IS function in house (same as splitting design and Silicon fabrication functions in 80&#8242;s in Chip business)</p>
<p>So from Amazon&#8217;s (and all our) viewpoint it makes sense -<br />
1) It lowers the entry barrier to users and developers to get into cloud.<br />
2) It enables faster adoption of cloud, and thereby brings in investment to further stimulate cloud tech development (remember Ford had said -&#8221;..they can have any color as they want as long as it is black&#8230;&#8221; about model T, whose standardization had helped build economy of scale and helped the auto industry)</p>
<p>The argument against RDS would have been stronger if the above analysis had done a comparison on economics and argued from business and strategic angles, rather than speculating that my own backup would be much better than Amazon&#8217;s professionally managed data centers.</p>
<p>Sure RDS is relational db thinking, which is not the cutting edge, but it still has its role to play (assuming the RDS is much faster that SimpleDB, else RDS and SimpleDB has to compete with each other)  Amazon should be careful against such possible internal conflict and canabalisation, and the RDS engineering team have to keep better latencies in RDS compared to SimpleDB, would be interesting to see how each team does that over next 3 years).<br />
I am sure Amazon&#8217;s executive may have thought about such Darwinian strategy to stimulate tech development internally.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
