In relation to another comment earlier on, if you're using OO methods to access the database, that can be a serious performance issue. If performance is a real problem for you, you may want to consider replacing Class::DBI or DBIx::Class with Rose::DB::Object. RDBO is considerably faster, as objective benchmarks have shown. I personally use DBIx::Class, but if performance was a more serious issue for me, I'd switch.

Also, I'd highly recommend investigating PostgreSQL for this application. MySQL has its place, but this may not be a good match for it. PostgreSQL scales better under heavy transactional loads, and is generally a much more rigorous, professional-grade, extensible, and standardized solution than MySQL. Prior to the recent release of MySQL 5, I would have said you'd be crazy to run this on MySQL at all. It's still crazy to run it on 4.x. Either upgrade to 5, or switch to PostgreSQL. My opinion on the matter strongly leans towards PostgreSQL. It's just my opinion, but it's backed by a lot of experience with high-performance transactional RDBMS's from various vendors. (Oh, and if you make the switch, be sure to use PostgreSQL 8.1, no sense going through all the trouble of switching over and then using something outdated).

In reply to Re: OT: Scalable web application architecture by ph713
in thread OT: Scalable web application architecture by badaiaqrandista

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.