Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the cele domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/hughmcguire/hughmcguire.net/wp-includes/functions.php on line 6260
Comments on: scaling ruby on rails https://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/ aging idealist. ai and education, open web, open publishing. Sat, 11 Aug 2007 04:14:51 +0000 hourly 1 https://wordpress.org/?v=7.1.5 By: rabb5 https://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/comment-page-1/#comment-1082 Sat, 11 Aug 2007 04:14:51 +0000 https://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/#comment-1082 I found another post which is worth looking at that discusses scaling the logger facility, much like twitter does it:

http://www.dotrb.com/2007/8/11/scaling-rails-with-sysloglogger

]]>
By: Josh https://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/comment-page-1/#comment-372 Fri, 20 Apr 2007 23:17:58 +0000 https://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/#comment-372 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.

]]>
By: Hugh https://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/comment-page-1/#comment-343 Sat, 14 Apr 2007 17:44:42 +0000 https://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/#comment-343 s no facility in Rails to talk to more than one database at a time."]]> 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 & 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.”

]]>
By: heri https://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/comment-page-1/#comment-342 Fri, 13 Apr 2007 22:30:44 +0000 https://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/#comment-342 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

]]>
By: Chris Hughes https://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/comment-page-1/#comment-341 Fri, 13 Apr 2007 16:21:07 +0000 https://hughmcguire.net/2007/04/13/scaling-ruby-on-rails/#comment-341 The Ruby on Rails people have a great ebook about web app development available here: http://gettingreal.37signals.com/

]]>