<?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: Queue everything and delight everyone</title>
	<atom:link href="http://decafbad.com/blog/2008/07/04/queue-everything-and-delight-everyone/feed" rel="self" type="application/rss+xml" />
	<link>http://decafbad.com/blog/2008/07/04/queue-everything-and-delight-everyone</link>
	<description>It's all spinning wheels and self-doubt until the first pot of coffee.</description>
	<lastBuildDate>Fri, 19 Mar 2010 00:06:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0-alpha</generator>
	<item>
		<title>By: Levy Carneiro &#187; Blog Archive &#187; Flickr engineers do it offline</title>
		<link>http://decafbad.com/blog/2008/07/04/queue-everything-and-delight-everyone/comment-page-1#comment-407439</link>
		<dc:creator>Levy Carneiro &#187; Blog Archive &#187; Flickr engineers do it offline</dc:creator>
		<pubDate>Tue, 16 Jun 2009 02:54:04 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/?p=1194#comment-407439</guid>
		<description>&lt;p&gt;[...] seems that using queuing systems in web apps is the new hottness . While the basic idea itself certainly isn’t new, its application to modern, large, scalable [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] seems that using queuing systems in web apps is the new hottness . While the basic idea itself certainly isn’t new, its application to modern, large, scalable [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Henry</title>
		<link>http://decafbad.com/blog/2008/07/04/queue-everything-and-delight-everyone/comment-page-1#comment-406951</link>
		<dc:creator>Chris Henry</dc:creator>
		<pubDate>Thu, 11 Jun 2009 20:09:47 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/?p=1194#comment-406951</guid>
		<description>&lt;p&gt;Handling load is probably one of the biggest problems facing websites today.  Queueing is definitely the way to go, but like you said, sites need the type of architecture where it&#039;s easy to deploy services to different machines.  Usually by the time the site is under load, it&#039;s too late...&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Handling load is probably one of the biggest problems facing websites today.  Queueing is definitely the way to go, but like you said, sites need the type of architecture where it&#8217;s easy to deploy services to different machines.  Usually by the time the site is under load, it&#8217;s too late&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jmxz</title>
		<link>http://decafbad.com/blog/2008/07/04/queue-everything-and-delight-everyone/comment-page-1#comment-388343</link>
		<dc:creator>jmxz</dc:creator>
		<pubDate>Fri, 13 Feb 2009 20:00:13 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/?p=1194#comment-388343</guid>
		<description>&lt;p&gt;Wow those comments make me feel old.  I remember when these java queues everyone&#039;s referring to reminded me of how I had a VAX dedicated to queuing and scheduling batch jobs for a Cray.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Wow those comments make me feel old.  I remember when these java queues everyone&#8217;s referring to reminded me of how I had a VAX dedicated to queuing and scheduling batch jobs for a Cray.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay Yukes</title>
		<link>http://decafbad.com/blog/2008/07/04/queue-everything-and-delight-everyone/comment-page-1#comment-378544</link>
		<dc:creator>Jay Yukes</dc:creator>
		<pubDate>Sun, 23 Nov 2008 10:35:55 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/?p=1194#comment-378544</guid>
		<description>&lt;p&gt;I had to solve a similar problem.  Needed the fastest possible response, so had to rule out interacting with the Database directly from the web app.  Used PHP message queue Dropr to defer all DB work.  It is very fast, easily over 1000 messages/second&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I had to solve a similar problem.  Needed the fastest possible response, so had to rule out interacting with the Database directly from the web app.  Used PHP message queue Dropr to defer all DB work.  It is very fast, easily over 1000 messages/second</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Seitz</title>
		<link>http://decafbad.com/blog/2008/07/04/queue-everything-and-delight-everyone/comment-page-1#comment-363382</link>
		<dc:creator>Bill Seitz</dc:creator>
		<pubDate>Mon, 28 Jul 2008 21:23:06 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/?p=1194#comment-363382</guid>
		<description>&lt;p&gt;I wonder if you&#039;re still setting the bar too high for low-priority connections. I mean, microblogging &lt;em&gt;isn&#039;t&lt;/em&gt; really messaging, and maybe isn&#039;t (shouldn&#039;t-be?) conversation. &lt;/p&gt;

&lt;p&gt;So why wouldn&#039;t 10-15min be good enough?&lt;/p&gt;

&lt;p&gt;What % of &quot;messages&quot; are &lt;em&gt;read&lt;/em&gt; instantly after they hit an inbox?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I wonder if you&#8217;re still setting the bar too high for low-priority connections. I mean, microblogging <em>isn&#8217;t</em> really messaging, and maybe isn&#8217;t (shouldn&#8217;t-be?) conversation. </p>
<p>So why wouldn&#8217;t 10-15min be good enough?</p>
<p>What % of &#8220;messages&#8221; are <em>read</em> instantly after they hit an inbox?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Extenuating Circumstances &#8211; links for 2008-07-15</title>
		<link>http://decafbad.com/blog/2008/07/04/queue-everything-and-delight-everyone/comment-page-1#comment-361484</link>
		<dc:creator>Extenuating Circumstances &#8211; links for 2008-07-15</dc:creator>
		<pubDate>Tue, 15 Jul 2008 10:47:51 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/?p=1194#comment-361484</guid>
		<description>&lt;p&gt;[...] 0xDECAFBAD » Queue everything and delight everyone Yes. (tags: queues asynchronous userinterface responsiveness decafbad blog) [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] 0xDECAFBAD » Queue everything and delight everyone Yes. (tags: queues asynchronous userinterface responsiveness decafbad blog) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: People Over Process &#187; links for 2008-07-12</title>
		<link>http://decafbad.com/blog/2008/07/04/queue-everything-and-delight-everyone/comment-page-1#comment-361188</link>
		<dc:creator>People Over Process &#187; links for 2008-07-12</dc:creator>
		<pubDate>Sat, 12 Jul 2008 07:31:41 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/?p=1194#comment-361188</guid>
		<description>&lt;p&gt;[...] Queue everything and delight everyone &#8220;[D]o you really have to do everything all at once?&#8221; (tags: queue messaging architecture programming twitter) [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] Queue everything and delight everyone &#8220;[D]o you really have to do everything all at once?&#8221; (tags: queue messaging architecture programming twitter) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: citric</title>
		<link>http://decafbad.com/blog/2008/07/04/queue-everything-and-delight-everyone/comment-page-1#comment-361031</link>
		<dc:creator>citric</dc:creator>
		<pubDate>Thu, 10 Jul 2008 21:49:19 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/?p=1194#comment-361031</guid>
		<description>&lt;p&gt;Web apps doing things while the user waits unnecessarily is an old phenomenon. I think it&#039;s often a matter of developers not wanting to (and/or being politically unable to) venture into what they consider the sysadmin&#039;s domain. Take the way-too-common case of apps that make the client wait while it does housekeeping. Why isn&#039;t this in a cron job? One reason is maybe this is KewlOSSBlogWikiPackage and it&#039;s simpler to say &quot;just untar the package under htdocs and you&#039;re done&quot; instead of saying &quot;also, unpack these scripts in a non-servable area and set them up to run hourly, but not all at the same time; stagger them a little. And run them with the same UID your web server is running as&quot;. But we end up with a lot of apps that (badly) reimplement basic tools their OS ships with in the first place.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Web apps doing things while the user waits unnecessarily is an old phenomenon. I think it&#8217;s often a matter of developers not wanting to (and/or being politically unable to) venture into what they consider the sysadmin&#8217;s domain. Take the way-too-common case of apps that make the client wait while it does housekeeping. Why isn&#8217;t this in a cron job? One reason is maybe this is KewlOSSBlogWikiPackage and it&#8217;s simpler to say &#8220;just untar the package under htdocs and you&#8217;re done&#8221; instead of saying &#8220;also, unpack these scripts in a non-servable area and set them up to run hourly, but not all at the same time; stagger them a little. And run them with the same UID your web server is running as&#8221;. But we end up with a lot of apps that (badly) reimplement basic tools their OS ships with in the first place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://decafbad.com/blog/2008/07/04/queue-everything-and-delight-everyone/comment-page-1#comment-360996</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Thu, 10 Jul 2008 13:36:22 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/?p=1194#comment-360996</guid>
		<description>&lt;p&gt;I agree with everything you&#039;ve said. Especially the last part, duplicating data in the format it will be retrieved in rather than using complicated and CPU intensive SQL queries. This is especially true for any sort of statistics or reporting. I learned this by seeing my website&#039;s statistics growing slower and slower to retrieve as more and more traffic caused the database to become larger and larger and all of a sudden those queries that ran nearly instantly, even with good indexing were taking several seconds to return.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I agree with everything you&#8217;ve said. Especially the last part, duplicating data in the format it will be retrieved in rather than using complicated and CPU intensive SQL queries. This is especially true for any sort of statistics or reporting. I learned this by seeing my website&#8217;s statistics growing slower and slower to retrieve as more and more traffic caused the database to become larger and larger and all of a sudden those queries that ran nearly instantly, even with good indexing were taking several seconds to return.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alexis</title>
		<link>http://decafbad.com/blog/2008/07/04/queue-everything-and-delight-everyone/comment-page-1#comment-360987</link>
		<dc:creator>alexis</dc:creator>
		<pubDate>Thu, 10 Jul 2008 12:35:25 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/?p=1194#comment-360987</guid>
		<description>&lt;p&gt;er... eventually consistent social graphs anyone?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>er&#8230; eventually consistent social graphs anyone?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brent Fitzgerald / Life &#38; Research Notes / Blog Archive &#187; Links for July 3rd through July 9th</title>
		<link>http://decafbad.com/blog/2008/07/04/queue-everything-and-delight-everyone/comment-page-1#comment-360929</link>
		<dc:creator>Brent Fitzgerald / Life &#38; Research Notes / Blog Archive &#187; Links for July 3rd through July 9th</dc:creator>
		<pubDate>Wed, 09 Jul 2008 18:02:23 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/?p=1194#comment-360929</guid>
		<description>&lt;p&gt;[...] 0xDECAFBAD &#187; Queue everything and delight everyone interesting blog post on architectures for scalability of microblogging and messaging/publishing. argues for queue systems over sql queries, which is reasonable. consider extensibility of the queue processors as the hook for new apps/innovations. article blog microblogging scalability twitter web [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] 0xDECAFBAD &raquo; Queue everything and delight everyone interesting blog post on architectures for scalability of microblogging and messaging/publishing. argues for queue systems over sql queries, which is reasonable. consider extensibility of the queue processors as the hook for new apps/innovations. article blog microblogging scalability twitter web [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A Couple of Caveats on Queuing - Laughing Meme</title>
		<link>http://decafbad.com/blog/2008/07/04/queue-everything-and-delight-everyone/comment-page-1#comment-360758</link>
		<dc:creator>A Couple of Caveats on Queuing - Laughing Meme</dc:creator>
		<pubDate>Mon, 07 Jul 2008 18:02:56 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/?p=1194#comment-360758</guid>
		<description>&lt;p&gt;[...] &#8220;Delight Everyone&#8221; post is latest greatest addition to the 17th letter of the alphabet for savior [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] &#8220;Delight Everyone&#8221; post is latest greatest addition to the 17th letter of the alphabet for savior [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: text/plain &#187; Blog Archive &#187; 3,737,844,653</title>
		<link>http://decafbad.com/blog/2008/07/04/queue-everything-and-delight-everyone/comment-page-1#comment-360721</link>
		<dc:creator>text/plain &#187; Blog Archive &#187; 3,737,844,653</dc:creator>
		<pubDate>Mon, 07 Jul 2008 07:47:59 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/?p=1194#comment-360721</guid>
		<description>&lt;p&gt;[...] L. M. Orchard writes the following in an otherwise quite sensible article on queue-based architectures for broadcast messaging systems: &#8220;Even with these delays, the system is still better at getting the word out than the original content creator would be at notifying all the others involved with an out-of-band system like IM or email.&#8221; [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] L. M. Orchard writes the following in an otherwise quite sensible article on queue-based architectures for broadcast messaging systems: &#8220;Even with these delays, the system is still better at getting the word out than the original content creator would be at notifying all the others involved with an out-of-band system like IM or email.&#8221; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Don Park</title>
		<link>http://decafbad.com/blog/2008/07/04/queue-everything-and-delight-everyone/comment-page-1#comment-360597</link>
		<dc:creator>Don Park</dc:creator>
		<pubDate>Sun, 06 Jul 2008 05:16:32 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/?p=1194#comment-360597</guid>
		<description>&lt;p&gt;Good suggestions. For social services like Twitter, I would also add one more item:&lt;/p&gt;

&lt;p&gt;Prioritize by Relationship&lt;/p&gt;

&lt;p&gt;For example, two-way Twitter relationships (mutual-follow or recent @ or direct message exchange) should be refreshed before one-way. One can go further by placing higher priority on users whom poster sent messages to or received from within past X-hours.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Good suggestions. For social services like Twitter, I would also add one more item:</p>
<p>Prioritize by Relationship</p>
<p>For example, two-way Twitter relationships (mutual-follow or recent @ or direct message exchange) should be refreshed before one-way. One can go further by placing higher priority on users whom poster sent messages to or received from within past X-hours.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Infovore &#187; links for 2008-07-05</title>
		<link>http://decafbad.com/blog/2008/07/04/queue-everything-and-delight-everyone/comment-page-1#comment-360572</link>
		<dc:creator>Infovore &#187; links for 2008-07-05</dc:creator>
		<pubDate>Sat, 05 Jul 2008 23:30:32 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/?p=1194#comment-360572</guid>
		<description>&lt;p&gt;[...] 0xDECAFBAD » Queue everything and delight everyone  &#8220;&#8230;that&#8217;s really the purpose of a web-based content creation interface—accepting something as quickly as possible to make the user happy enough to continue submitting more.&#8221; Leslie Orchard on message-queue-based design. (tags: queue messaging development software programming architecture) [...]&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>[...] 0xDECAFBAD » Queue everything and delight everyone  &#8220;&#8230;that&#8217;s really the purpose of a web-based content creation interface—accepting something as quickly as possible to make the user happy enough to continue submitting more.&#8221; Leslie Orchard on message-queue-based design. (tags: queue messaging development software programming architecture) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
