<?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"
	>
<channel>
	<title>Comments on: How YouTube scales MySQL for its large databases</title>
	<atom:link href="http://ebiquity.umbc.edu/blogger/2007/12/28/how-youtube-scales-mysql-for-its-large-databases/feed/" rel="self" type="application/rss+xml" />
	<link>http://ebiquity.umbc.edu/blogger/2007/12/28/how-youtube-scales-mysql-for-its-large-databases/</link>
	<description>EBB is the ebiquity research group\\\'s blog at the University of Maryland, Baltimore County (UMBC).  We focus on technologies that facilitate the design, implementation and control of distributed, intelligent information systems -- mobile and pervasive computing, ad hoc networking, multiagent systems, knowledge representation and reasoning, and the semantic web.  As the tides of technology ebb and flow, we hope the good ideas wash up on our beach and the bad ones drift back out to sea.</description>
	<pubDate>Sat, 05 Jul 2008 03:31:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Floyd Price</title>
		<link>http://ebiquity.umbc.edu/blogger/2007/12/28/how-youtube-scales-mysql-for-its-large-databases/#comment-16264</link>
		<dc:creator>Floyd Price</dc:creator>
		<pubDate>Mon, 31 Dec 2007 15:18:59 +0000</pubDate>
		<guid isPermaLink="false">http://ebiquity.umbc.edu/blogger/2007/12/28/how-youtube-scales-mysql-for-its-large-databases/#comment-16264</guid>
		<description>Its good to see website with this much traffic sticking with MySQL :-)</description>
		<content:encoded><![CDATA[<p>Its good to see website with this much traffic sticking with MySQL <img src='http://ebiquity.umbc.edu/blogger/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Trevena</title>
		<link>http://ebiquity.umbc.edu/blogger/2007/12/28/how-youtube-scales-mysql-for-its-large-databases/#comment-16260</link>
		<dc:creator>Aaron Trevena</dc:creator>
		<pubDate>Mon, 31 Dec 2007 12:07:54 +0000</pubDate>
		<guid isPermaLink="false">http://ebiquity.umbc.edu/blogger/2007/12/28/how-youtube-scales-mysql-for-its-large-databases/#comment-16260</guid>
		<description>@James,

It's a case of picking the right tool for the job - I've worked on two high availability sites for different clients in different markets this year : Aviation Briefings for airlines, etc and Online Classifieds - one required Postgres, one required MySQL.

Horses for courses - quite simply - for this kind of task mysql beats postgres in terms of ease of scaling, query caching, etc - when you're dealing with very high traffic, then you're better off breaking up and simplifying your schema, etc in order to get the most speed, than using the "more powerful" RDBMS.</description>
		<content:encoded><![CDATA[<p>@James,</p>
<p>It&#8217;s a case of picking the right tool for the job - I&#8217;ve worked on two high availability sites for different clients in different markets this year : Aviation Briefings for airlines, etc and Online Classifieds - one required Postgres, one required MySQL.</p>
<p>Horses for courses - quite simply - for this kind of task mysql beats postgres in terms of ease of scaling, query caching, etc - when you&#8217;re dealing with very high traffic, then you&#8217;re better off breaking up and simplifying your schema, etc in order to get the most speed, than using the &#8220;more powerful&#8221; RDBMS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://ebiquity.umbc.edu/blogger/2007/12/28/how-youtube-scales-mysql-for-its-large-databases/#comment-16230</link>
		<dc:creator>James</dc:creator>
		<pubDate>Sat, 29 Dec 2007 03:26:22 +0000</pubDate>
		<guid isPermaLink="false">http://ebiquity.umbc.edu/blogger/2007/12/28/how-youtube-scales-mysql-for-its-large-databases/#comment-16230</guid>
		<description>Because you know, the choice is always between the free, feature-poor, fast at 'select * from table' dbms and the expensive, scalable, feature-rich dbms.  There couldn't possible be a free, feature-rich, scalable dbms out there that you could use.  Of course not.</description>
		<content:encoded><![CDATA[<p>Because you know, the choice is always between the free, feature-poor, fast at &#8217;select * from table&#8217; dbms and the expensive, scalable, feature-rich dbms.  There couldn&#8217;t possible be a free, feature-rich, scalable dbms out there that you could use.  Of course not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce</title>
		<link>http://ebiquity.umbc.edu/blogger/2007/12/28/how-youtube-scales-mysql-for-its-large-databases/#comment-16217</link>
		<dc:creator>Bruce</dc:creator>
		<pubDate>Fri, 28 Dec 2007 17:24:02 +0000</pubDate>
		<guid isPermaLink="false">http://ebiquity.umbc.edu/blogger/2007/12/28/how-youtube-scales-mysql-for-its-large-databases/#comment-16217</guid>
		<description>Hi,

have a look at http://highscalability.com/ for more examples of LAMP, JAVA, etc architectures and why you don't need to go down the DB2, Oracle, etc route to get high load sites off the ground. If Flickr, etc, don't use them, why should we?</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>have a look at <a href="http://highscalability.com/" rel="nofollow">http://highscalability.com/</a> for more examples of LAMP, JAVA, etc architectures and why you don&#8217;t need to go down the DB2, Oracle, etc route to get high load sites off the ground. If Flickr, etc, don&#8217;t use them, why should we?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
