<?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/"
		>
<channel>
	<title>Comments on: BigTable Thoughts</title>
	<atom:link href="http://www.pythian.com/news/1034/bigtable-thoughts/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pythian.com/news/1034/bigtable-thoughts/</link>
	<description>News and views from Pythian DBAs</description>
	<lastBuildDate>Sat, 20 Mar 2010 20:27:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Alex Gorbachev</title>
		<link>http://www.pythian.com/news/1034/bigtable-thoughts/#comment-209531</link>
		<dc:creator>Alex Gorbachev</dc:creator>
		<pubDate>Sat, 31 May 2008 20:14:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.pythian.com/blogs/1034/bigtable-thoughts#comment-209531</guid>
		<description>&lt;i&gt;So using this thinking, every time someone I follow (say, @paulandstorm) makes a comment, it not only writes to their shard, but to mine. Now, that may not work given that the system also has to send messages at the same time, and that there can be numerous followers â€” dozens, hundreds, thousands.&lt;/i&gt;

And here is when async processing might come useful -- when paulandstorm makes a comment, it&#039;s written to its own shard and queued for propagation to the followers. This queue can be worked off in a more optimal way in the background.</description>
		<content:encoded><![CDATA[<p><i>So using this thinking, every time someone I follow (say, @paulandstorm) makes a comment, it not only writes to their shard, but to mine. Now, that may not work given that the system also has to send messages at the same time, and that there can be numerous followers â€” dozens, hundreds, thousands.</i></p>
<p>And here is when async processing might come useful &#8212; when paulandstorm makes a comment, it&#8217;s written to its own shard and queued for propagation to the followers. This queue can be worked off in a more optimal way in the background.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
