Many interesting posts here. Thanks for sharing. To me, it's the total "stack" that counts, since everything from the OS to the database to the net setup (such as DDOS protection and handling), to the actual Perl code that runs behind your web pages all comes together in an implementation that defines how well a web app does or doesn't perform in the real world.

These kinds of post in this thread, sharing real world experiences and implementation details of the "stack" components (OS, database, etc.) people find work well, make us all better Perl Monks, IMO.

Right now, I'm reading up on DDOS defenses. Interesting stuff (feel free to offer suggestions and links).

In reply to Re: OpenBSD or FreeBSD for a Perl web app Production platform? by Anonymous Monk
in thread OpenBSD or FreeBSD for a Perl web app Production platform? by Anonymous Monk

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.