<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/stylesheets/rss.css" type="text/css"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
  <channel>
    <title>Spoken: Distributed Ruby Workers on EC2</title>
    <link>http://spoken.phrasewise.com/articles/2007/05/15/distributed-ruby-workers-on-ec2</link>
    <language>en-us</language>
    <ttl>40</ttl>
    <description>Daniel Berlinger :: helpless :: speechless :: breathless</description>
    <item>
      <title>Distributed Ruby Workers on EC2</title>
      <description>&lt;div class="entry" title="Distributed Ruby Workers on EC2 - igvita.com" link="http://www.igvita.com/blog/2007/05/15/distributed-ruby-workers-on-ec2/"&gt;
&lt;a href="http://www.igvita.com/blog/2007/05/15/distributed-ruby-workers-on-ec2/"&gt;Distributed Ruby Workers on EC2&lt;/a&gt;: Simply put, DRb allows you to interact with remote objects via TCP as if they were located right on your system. Hence, to avoid locking our server, we will simply get another computer to perform the time-consuming task for us. Of course, now you&amp;rsquo;re saying: where am I going to get another computer? Well, how about Amazon&amp;rsquo;s EC2 &lt;cite cite="http://www.igvita.com/blog/2007/05/15/distributed-ruby-workers-on-ec2/" title="Daniel's remark..." class="dRemark"&gt;[EC2 is clearly a game changer.]&lt;/cite&gt;  
&lt;/div&gt;</description>
      <pubDate>Tue, 15 May 2007 15:02:00 +0000</pubDate>
      <guid isPermaLink="false">urn:uuid:ebaaccb1-1a76-4747-9237-4d2570081bb1</guid>
      <author>Daniel</author>
      <link>http://spoken.phrasewise.com/articles/2007/05/15/distributed-ruby-workers-on-ec2</link>
      <category>code</category>
      <category>news</category>
      <category>design</category>
      <category>tech</category>
      <trackback:ping>http://spoken.phrasewise.com/articles/trackback/577</trackback:ping>
    </item>
  </channel>
</rss>
