Ours is a REST based service so every request has business logic and an apache+mod_perl instance actually has a better segregation of the webserver and Perl code - we don't worry about handling the HTTP request and managing children. We trust Apache will do the right thing and if something breaks we have a large community of people who can help. All we worry about is our business logic which well no one can help if we don't know what we have coded :)
Would you like to share a Perl based webserver which can be guaranteed to be comparable to apache in terms of reliability and stability ? On Tue, Aug 4, 2020 at 3:48 PM Mark Blackman <m...@blackmans.org> wrote: > > > On 4 Aug 2020, at 21:41, Mithun Bhattacharya <mit...@gmail.com> wrote: > > I am genuinely curious what are these other "well known" means ? > > On Tue, Aug 4, 2020 at 3:37 PM Mark Blackman <m...@blackmans.org> wrote: > >> >> >> > On 4 Aug 2020, at 17:58, Mithun Bhattacharya <mit...@gmail.com> wrote: >> > >> > mod_perl does have value because it does a more efficient utilization >> of resources - this is important when fast response time and scalability is >> important. The complexity is a known problem but it is not a mystery box >> either - there is enough documentation which explains what has to happen >> and what could have gone wrong. >> >> mod_perl’s relative efficiency can be achieved by other well-known means. > > > That would depend on what you mean by "efficient utilisation of > resources”. You can get the same general effect, more simply, by running a > high-performing pre-forking Perl web application server and a web server > with a simple configuration in front of it ,instead of a complicated > Apache+mod_perl installation. > > That also buys you a nice separation of concerns, the web server handles > all the complicated host or path rewrites and access control and the Perl > app focuses on responding to the, now-sanitised, fully normalized, HTTP > requests. > > - Mark > > > >
