<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Hey Twitter! Your problems are my problems!</title>
	<atom:link href="http://blog.ryantoohil.com/2008/06/hey-twitter-your-problems-are-my-problems.php/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.ryantoohil.com/2008/06/hey-twitter-your-problems-are-my-problems.php</link>
	<description>Stuff.</description>
	<lastBuildDate>Thu, 11 Feb 2010 16:01:40 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: eric</title>
		<link>http://blog.ryantoohil.com/2008/06/hey-twitter-your-problems-are-my-problems.php/comment-page-1#comment-15944</link>
		<dc:creator>eric</dc:creator>
		<pubDate>Tue, 10 Jun 2008 12:09:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ryantoohil.com/?p=275#comment-15944</guid>
		<description>Google BigTables does this automatically.  Google&#039;s AppEngine platform is opening up sharding to us plebeians so we don&#039;t have to learn how to configure MySQL for sharding (a quick google search for the topic didn&#039;t yield any obvious tutorials last week). While there are other technical problems with AppEngine platform at the present time, such as migrating data forward when you made a Model/Schema change, it does start to teach normal developers the logic and the reasoning behind sharding.  Two weeks ago at Google I/O, one of the team members gave a good introductory talk on how to use sharding.    In fact, on the AppEngine plaform, you can&#039;t join across tables because of the performance impact.  I wonder how far away open source database such as CouchDb are from picking up the performance such that they could be considered a viable alternative to relational databases.  The last I read, CouchDb has such an abysmal write throughput that it has a _long_ way to go.</description>
		<content:encoded><![CDATA[<p>Google BigTables does this automatically.  Google&#8217;s AppEngine platform is opening up sharding to us plebeians so we don&#8217;t have to learn how to configure MySQL for sharding (a quick google search for the topic didn&#8217;t yield any obvious tutorials last week). While there are other technical problems with AppEngine platform at the present time, such as migrating data forward when you made a Model/Schema change, it does start to teach normal developers the logic and the reasoning behind sharding.  Two weeks ago at Google I/O, one of the team members gave a good introductory talk on how to use sharding.    In fact, on the AppEngine plaform, you can&#8217;t join across tables because of the performance impact.  I wonder how far away open source database such as CouchDb are from picking up the performance such that they could be considered a viable alternative to relational databases.  The last I read, CouchDb has such an abysmal write throughput that it has a _long_ way to go.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Toohil</title>
		<link>http://blog.ryantoohil.com/2008/06/hey-twitter-your-problems-are-my-problems.php/comment-page-1#comment-15934</link>
		<dc:creator>Ryan Toohil</dc:creator>
		<pubDate>Tue, 03 Jun 2008 23:39:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ryantoohil.com/?p=275#comment-15934</guid>
		<description>No, we should just go start our own company. Then we will never need to make resumes again.</description>
		<content:encoded><![CDATA[<p>No, we should just go start our own company. Then we will never need to make resumes again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jason</title>
		<link>http://blog.ryantoohil.com/2008/06/hey-twitter-your-problems-are-my-problems.php/comment-page-1#comment-15933</link>
		<dc:creator>jason</dc:creator>
		<pubDate>Tue, 03 Jun 2008 21:31:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.ryantoohil.com/?p=275#comment-15933</guid>
		<description>This would make a lovely cover letter for a resume.</description>
		<content:encoded><![CDATA[<p>This would make a lovely cover letter for a resume.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
