Re: Coupling Plack/PSGI with mod_perl, or an alternate architecture?

On Wed, Oct 10, 2012 at 12:39 PM, Perrin Harkins <[email protected]> wrote:
>> 2) Do you believe that there are any compelling reasons to pick a mod_perl
>> approach over a plack runner approach that we may be missing?
>
> Advantages of a mod_perl approach:
> - Access to all the mod_perl stuff on CPAN (auth modules, SizeLimit,
> rate-limiting, etc.).
> - Ability to use the Apache API when handling requests.
> - Sounds like at least some of your team has real-life experience
> running a site on mod_perl.

- Knowledge that the base Apache httpd codebase is used by many other
websites, and has been through security audits, performance tuning,
and is composed of a set of developers who are committed to the long
term health of the codebase.

- A stable history of distribution packaging. Odds are the platform
you are using has mod_perl / Apache rpms/deb/ebuilds/etc for quite
some time.

- Knowledge that mod_perl has been proven in large scale deployments.
The biggest I've worked on is about 500 servers if I recall correctly.