CgiApp will have a smaller footprint as it uses less modules and, frankly, does
less. That said, the Catalyst devteam is very keen on scaling. Now, a major piece of this is how you deploy. Most CgiApp deployments that I've seen/heard about are done under mod_perl. Catalyst tends to deploy under FCGI. That can make a huge difference in your overall memory footprint (MP is often better) and scalability (FCGI is designed around scalability). As for HUGE number of hits, I'd say they can both handle it.
And, if expressivity wasn't important, you'd be using C and not Perl. Plus, Lisp often beats out C in the Language Shootout. We don't use Lisp because it's not fashionable enough to have a big enough ecology around it. Perl is Lisp minus a few features, but plus CPAN. Perl 6 is meant to be Lisp + CPAN, no minuses.
My criteria for good software:
- Does it work?
- Can someone else come in, make a change, and be reasonably certain no bugs were introduced?
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||