People use nginx - probably because they haven't come across mpm_event. The two are I think comparable speed wise, but out of the box mpm_event is more flexible - and the nice thing is that you can develop a site on a single mpm_worker instance and easily migrate over to the mpm_event/mpm_worker module.
It is nice to use the same configuration language on both sites... mpm_event like all Apache mpm_s is much better at handling "issues" where nginx just goes F* and returns nothing. When we have issues we can detect them on apache mpms - but we often fail to see nginx errors as it sort of just dies! -----Original Message----- From: pengyh <pen...@mail.de> Sent: 09 August 2022 13:04 To: James Smith <j...@sanger.ac.uk>; modperl@perl.apache.org Subject: Re: is mpm_event safe for modperl handler? [EXT] I think running Ignix as front-end server and mod_perl for backend server is the more popular choice. > If you want the speed of mod_event for static content and the power of > mod_perl for dynamic content - the best way is to run a lightweight mod_event > apache in front of a mod_prefork to run the mod_perl.... -- The Wellcome Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.
