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.
  • Two interesting things here are that none of them use PostgreSQL, despite a few of them being fairly new

    I agree here, PostgreSQL is not popular with scaling large websites. It's strengths are not well suited to that task. It is not nearly as fast as MySQL on reads, and is not as friendly as MySQL to setup for web developers. It is the hidden P in LAMP (although my version of LAMP is Linux Apache Mod_perl Postgresql).

    PostgreSQL is best suited for applications which require higher than 10 to 1 ratio or reads to writes. InnoDB provides a form of MVCC and locking, but imho the locking in PostgreSQL is much more robust and performant (and I'm not here to engage in the details of the differences with regards to the two). I've often seen MySQL and PostgreSQL as potentially complimentary systems, and using dbi-link they can function as such - one for reads and one for writes.

    I read through the Oreilly articles and it seems like most of the situations are pushing read heavy scenarios. That's the point at which you need to implement the hybrid solution that not a lot of people talk about. Craigslist gets by on myisam through a delayed insert approach (post to craigslist and you will see for yourself), and I'm guessing that the other scenarios have a delayed update scenario as well. That's the hard part - real time updates. It's something still relegated to the domain of web applications. Websites can still get by with delayed updates as the content is mostly static, and in any large deployment you don't want to depend on the database for the availability of your content.