NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
about I/O disciplines and I should retire to the Tassili-in-Aijer
mountains in Sahara as a camel herder :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
"talk to more than one database"? (Score:1)
What do you think he means by this? That the high-level Rails API makes it hard to work with multiple read-only slave dbs?
The basic statement he's making -- that you have to use caching and replication to scale database access once you can't fit it on one machine anymore -- is not specific to Ruby or Rails. It's the same story in Perl, PHP, Java, etc.
Maybe what he's really getting at is that ActiveRecord generates inefficient SQL, or is just impossible to use in a multi-db scenario.
Re:"talk to more than one database"? (Score:2)
The fact that Rails doesn't scale to multiple cores is a Ruby issue, not a Rails issue, and one that's certainly not unique to Ruby.
Reply to This
Parent