<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: workers</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/workers.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2009-11-04T20:20:13+00:00</updated><author><name>Simon Willison</name></author><entry><title>Introducing Resque</title><link href="https://simonwillison.net/2009/Nov/4/resque/#atom-tag" rel="alternate"/><published>2009-11-04T20:20:13+00:00</published><updated>2009-11-04T20:20:13+00:00</updated><id>https://simonwillison.net/2009/Nov/4/resque/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://github.com/blog/542-introducing-resque"&gt;Introducing Resque&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
A new background worker management queue developed at GitHub, using Redis for the persistence layer. The blog post explains both the design and the shortcomings of previous solutions at length. Within 24 hours of the release code an external developer, Adam Cooke, has completely reskinned the UI.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/github"&gt;github&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/open-source"&gt;open-source&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/queue"&gt;queue&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/redis"&gt;redis&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/resque"&gt;resque&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ruby"&gt;ruby&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/sinatra"&gt;sinatra&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/workers"&gt;workers&lt;/a&gt;&lt;/p&gt;



</summary><category term="github"/><category term="open-source"/><category term="queue"/><category term="redis"/><category term="resque"/><category term="ruby"/><category term="sinatra"/><category term="workers"/></entry><entry><title>cloud-crowd</title><link href="https://simonwillison.net/2009/Sep/21/cloudcrowd/#atom-tag" rel="alternate"/><published>2009-09-21T23:09:04+00:00</published><updated>2009-09-21T23:09:04+00:00</updated><id>https://simonwillison.net/2009/Sep/21/cloudcrowd/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://github.com/documentcloud/cloud-crowd"&gt;cloud-crowd&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
New parallel processing worker/job queue system with a strikingly elegant architecture. The central server is an HTTP server that manages job requests, which are farmed out to a number of node HTTP servers which fork off worker processes to do the work. All communication is webhook-style JSON, and the servers are implemented in Sinatra and Thin using a tiny amount of code. The web-based monitoring interface is simply beautiful, using canvas to display graphs showing the system’s overall activity.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/canvas"&gt;canvas&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/cloudcrowd"&gt;cloudcrowd&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/http"&gt;http&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/json"&gt;json&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/message-queues"&gt;message-queues&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/ruby"&gt;ruby&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/sinatra"&gt;sinatra&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/thin"&gt;thin&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/webhooks"&gt;webhooks&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/workers"&gt;workers&lt;/a&gt;&lt;/p&gt;



</summary><category term="canvas"/><category term="cloudcrowd"/><category term="http"/><category term="json"/><category term="message-queues"/><category term="ruby"/><category term="sinatra"/><category term="thin"/><category term="webhooks"/><category term="workers"/></entry><entry><title>Offline Processing on App Engine: a Look Ahead</title><link href="https://simonwillison.net/2009/May/20/google/#atom-tag" rel="alternate"/><published>2009-05-20T12:40:12+00:00</published><updated>2009-05-20T12:40:12+00:00</updated><id>https://simonwillison.net/2009/May/20/google/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://code.google.com/events/io/sessions/OfflineProcessingAppEngine.html"&gt;Offline Processing on App Engine: a Look Ahead&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
A session at IO next week: “App Engine was designed to run request-driven web applications, although this will change in the coming year with the release of a number of offline computing components. In this session, we’ll explore the task queue/executor model of computation and some of the more interesting applications.”


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/google"&gt;google&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/google-app-engine"&gt;google-app-engine&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/io"&gt;io&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/message-queues"&gt;message-queues&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/offlineprocessing"&gt;offlineprocessing&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/workers"&gt;workers&lt;/a&gt;&lt;/p&gt;



</summary><category term="google"/><category term="google-app-engine"/><category term="io"/><category term="message-queues"/><category term="offlineprocessing"/><category term="workers"/></entry><entry><title>Techniques for safely consuming external HTTP on demand?</title><link href="https://simonwillison.net/2007/Dec/15/programming/#atom-tag" rel="alternate"/><published>2007-12-15T12:29:07+00:00</published><updated>2007-12-15T12:29:07+00:00</updated><id>https://simonwillison.net/2007/Dec/15/programming/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://programming.reddit.com/info/62zuw/comments"&gt;Techniques for safely consuming external HTTP on demand?&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
I asked this question on programming.reddit.com yesterday and got some really insightful answers, including Joe Stump from Digg describing how Digg Images uses Danga’s Gearman worker queue.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/askreddit"&gt;askreddit&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/danga"&gt;danga&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/digg"&gt;digg&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/gearman"&gt;gearman&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/http"&gt;http&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/joe-stump"&gt;joe-stump&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/queue"&gt;queue&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/reddit"&gt;reddit&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/scaling"&gt;scaling&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/workers"&gt;workers&lt;/a&gt;&lt;/p&gt;



</summary><category term="askreddit"/><category term="danga"/><category term="digg"/><category term="gearman"/><category term="http"/><category term="joe-stump"/><category term="queue"/><category term="reddit"/><category term="scaling"/><category term="workers"/></entry></feed>