I had 8-9 apps running as custom mp2 modules (not really in any framework.) I did a few things in Catalyst, but it never really lit my candle. Perlbal for reverse proxy. I used Postgres a lot, but eventually realized that sqlite3 was good enough for what I was doing most of the time.
Of late, I've been wanting to go to PSGI or node.js, but I haven't taken the plunge yet. Many of my mod_perl apps relied on client-side PKI and SSL renegotiation, which I don't think can be done in PSGI, (or at least not well) and mod_perl really shines by having hooks for all phases of request handling. On Thu, Jun 16, 2011 at 12:01 AM, Fred Moyer <f...@redhotpenguin.com> wrote: > I'm interested in hearing about what application frameworks (Catalyst, > CGI::App, Mojolicious) are used here with mod_perl. Given the number > of emerging Perl based webservers on CPAN (in addition to Nginx, > lighty, etc), it seems like there are many more Perl web application > and webservers out there now than there were five years ago. > > I'll start. I have a couple of Apache::Dispatch based applications I > wrote. I also work on an Apache::ASP large codebase, and a couple of > different Catalyst based systems. All are running on mod_perl 2.0.4 > in production (the ops haven't upgraded to 2.0.5 yet). > > If I were to migrate, I would probably try out something like > Mojolicious on Plack on mod_perl2. Performance of mod_perl2 has never > been an issue to date, but I have Perlbal doing connection handling as > a reverse proxy. >