<?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"
	>
<channel>
	<title>Comments on: scaling ruby on rails</title>
	<atom:link href="http://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/feed/" rel="self" type="application/rss+xml" />
	<link>http://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/</link>
	<description>at the intersection of technology, philosophy, and politics (and some other things).</description>
	<pubDate>Wed, 20 Aug 2008 18:52:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: rabb5</title>
		<link>http://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/#comment-1082</link>
		<dc:creator>rabb5</dc:creator>
		<pubDate>Sat, 11 Aug 2007 04:14:51 +0000</pubDate>
		<guid isPermaLink="false">http://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/#comment-1082</guid>
		<description>I found another post which is worth looking at that discusses scaling the logger facility, much like twitter does it:

&lt;a href="http://www.dotrb.com/2007/8/11/scaling-rails-with-sysloglogger" rel="nofollow"&gt;http://www.dotrb.com/2007/8/11/scaling-rails-with-sysloglogger&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I found another post which is worth looking at that discusses scaling the logger facility, much like twitter does it:</p>
<p><a href="http://www.dotrb.com/2007/8/11/scaling-rails-with-sysloglogger" rel="nofollow">http://www.dotrb.com/2007/8/11/scaling-rails-with-sysloglogger</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Josh</title>
		<link>http://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/#comment-372</link>
		<dc:creator>Josh</dc:creator>
		<pubDate>Fri, 20 Apr 2007 23:17:58 +0000</pubDate>
		<guid isPermaLink="false">http://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/#comment-372</guid>
		<description>The Twitter experience was definitely interesting to read especially from the scaling perspective.

Current Ruby is relatively slow so the scaling translates into more necessary hardware power. However, Ruby 2.0 will include the YARV virtual machine and be much faster (IBM Toronto software Labs' Antonio Cangiano did a comparison of an early Ruby 2.0 trunk). Here, one should allow some time for Ruby on Rails using Ruby 2.0 to be stabilized. But the future perspectives are still astounding.

The best thing with Ruby and RoR currently is the speed of development and the ease of maintainance. That means that it is still wickedly easy to prototype, grow and maintain Web 2.0 apps using RoR. that a major advantage.</description>
		<content:encoded><![CDATA[<p>The Twitter experience was definitely interesting to read especially from the scaling perspective.</p>
<p>Current Ruby is relatively slow so the scaling translates into more necessary hardware power. However, Ruby 2.0 will include the YARV virtual machine and be much faster (IBM Toronto software Labs&#8217; Antonio Cangiano did a comparison of an early Ruby 2.0 trunk). Here, one should allow some time for Ruby on Rails using Ruby 2.0 to be stabilized. But the future perspectives are still astounding.</p>
<p>The best thing with Ruby and RoR currently is the speed of development and the ease of maintainance. That means that it is still wickedly easy to prototype, grow and maintain Web 2.0 apps using RoR. that a major advantage.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hugh</title>
		<link>http://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/#comment-343</link>
		<dc:creator>Hugh</dc:creator>
		<pubDate>Sat, 14 Apr 2007 17:44:42 +0000</pubDate>
		<guid isPermaLink="false">http://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/#comment-343</guid>
		<description>chris: thanks for the link, i know 37signals, but didn't know they wrote a book.

heri: i think you are right, any framework has its ups &#038; downs. but it's good to know where one of rails' downs is...namely:

"At this point in time there’s no facility in Rails to talk to more than one
database at a time."</description>
		<content:encoded><![CDATA[<p>chris: thanks for the link, i know 37signals, but didn&#8217;t know they wrote a book.</p>
<p>heri: i think you are right, any framework has its ups &#038; downs. but it&#8217;s good to know where one of rails&#8217; downs is&#8230;namely:</p>
<p>&#8220;At this point in time there’s no facility in Rails to talk to more than one<br />
database at a time.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: heri</title>
		<link>http://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/#comment-342</link>
		<dc:creator>heri</dc:creator>
		<pubDate>Fri, 13 Apr 2007 22:30:44 +0000</pubDate>
		<guid isPermaLink="false">http://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/#comment-342</guid>
		<description>i think any technology or framework would have problems handling twitter's usage

twitter is an 'extreme' example and most web projects will stumble upon other problems before having a problem with RoR</description>
		<content:encoded><![CDATA[<p>i think any technology or framework would have problems handling twitter&#8217;s usage</p>
<p>twitter is an &#8216;extreme&#8217; example and most web projects will stumble upon other problems before having a problem with RoR</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Hughes</title>
		<link>http://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/#comment-341</link>
		<dc:creator>Chris Hughes</dc:creator>
		<pubDate>Fri, 13 Apr 2007 16:21:07 +0000</pubDate>
		<guid isPermaLink="false">http://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/#comment-341</guid>
		<description>The Ruby on Rails people have a great ebook about web app development available here: http://gettingreal.37signals.com/</description>
		<content:encoded><![CDATA[<p>The Ruby on Rails people have a great ebook about web app development available here: <a href="http://gettingreal.37signals.com/" rel="nofollow">http://gettingreal.37signals.com/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
