Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • 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.

    • Read loudthinking.com for two followups by DHH to that post. I'd provide direct links, but they seem to be borked at the moment. Short answer: the multi-db connection "problem" was solved by Dr. Nic as a plugin shortly after.

      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.