<?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: Twitter open sources its MySQL secret sauce</title>
	<atom:link href="http://gigaom.com/2012/04/09/twitter-open-sources-its-mysql-secret-sauce/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2012/04/09/twitter-open-sources-its-mysql-secret-sauce/</link>
	<description></description>
	<lastBuildDate>Tue, 21 May 2013 06:31:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Derrick Harris</title>
		<link>http://gigaom.com/2012/04/09/twitter-open-sources-its-mysql-secret-sauce/#comment-828435</link>
		<dc:creator><![CDATA[Derrick Harris]]></dc:creator>
		<pubDate>Tue, 10 Apr 2012 13:47:07 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=509053#comment-828435</guid>
		<description><![CDATA[Chris,

Thanks a lot for the comment. You&#039;re certainly not alone in taking this approach, either.]]></description>
		<content:encoded><![CDATA[<p>Chris,</p>
<p>Thanks a lot for the comment. You&#8217;re certainly not alone in taking this approach, either.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kristopher Wong</title>
		<link>http://gigaom.com/2012/04/09/twitter-open-sources-its-mysql-secret-sauce/#comment-828192</link>
		<dc:creator><![CDATA[Kristopher Wong]]></dc:creator>
		<pubDate>Tue, 10 Apr 2012 01:05:59 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=509053#comment-828192</guid>
		<description><![CDATA[I also have to assume that Oracle would be slow to react and implement changes because highly scalable MySQl is competition with Oracle which is a lock for enterprise.  With these published change I am going to need to assume you could probably run an enterprise level application on MySQL with little to no issues.

Kudos to Twitter for championing open source products]]></description>
		<content:encoded><![CDATA[<p>I also have to assume that Oracle would be slow to react and implement changes because highly scalable MySQl is competition with Oracle which is a lock for enterprise.  With these published change I am going to need to assume you could probably run an enterprise level application on MySQL with little to no issues.</p>
<p>Kudos to Twitter for championing open source products</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Aniszczyk</title>
		<link>http://gigaom.com/2012/04/09/twitter-open-sources-its-mysql-secret-sauce/#comment-828184</link>
		<dc:creator><![CDATA[Chris Aniszczyk]]></dc:creator>
		<pubDate>Tue, 10 Apr 2012 00:42:07 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=509053#comment-828184</guid>
		<description><![CDATA[Just to further expand why we did this (and not directly post patches to MySQL upstream), most of the changes apply generally and would be beneficial to the MySQL codebase. However, it&#039;s easier for us to go ahead and work in the open and to be able to pass these changes upstream, rather than pass them off privately and wait potentially a year or more to get them back in a public release. On top of that, we want to be able to collaborate with Percona, Facebook, Google, MariaDB, etc., on some of the actual changes, to make things better for everyone.

This is simply the first step towards that goal.]]></description>
		<content:encoded><![CDATA[<p>Just to further expand why we did this (and not directly post patches to MySQL upstream), most of the changes apply generally and would be beneficial to the MySQL codebase. However, it&#8217;s easier for us to go ahead and work in the open and to be able to pass these changes upstream, rather than pass them off privately and wait potentially a year or more to get them back in a public release. On top of that, we want to be able to collaborate with Percona, Facebook, Google, MariaDB, etc., on some of the actual changes, to make things better for everyone.</p>
<p>This is simply the first step towards that goal.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
