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.
  • Not Convinced (Score:2, Interesting)

    by chromatic (983) on 2003.03.24 13:14 (#18259) Homepage Journal
    And even if you think you can get by with MySQL, who is to say that you won't need more features later?

    I think you could just as easily say, even if you think you can get by with PostgreSQL, who is to say that you won't need more features later?

    I had a recent meeting with a big company who wants to do something interesting with Wikis and weblogs. The original Wiki is written in a couple of hundred lines of Perl and uses flatfiles to store the pages. Ward said he'd tried DBM but it was actually slower. He estimates some five thousand regular readers per day, perhaps up to a page served every second -- off of one box. There are ways to cluster read-only web boxes so you can add them easily, saving one beefy box for much-less frequent writes. It's fairly scalable.

    As for weblogs, some use flat files, and a few others use MySQL. Lots are written in Perl.

    The big company has bought into Java big time. Their SAs weren't thrilled with the Perl idea. That's fine; it's not difficult to port something simple like a Wiki or a weblog. It'll take time (which they don't have), but it's workable.

    The other requirement was... Oracle.

    No flat files, just a heckuva database backend.