Sounds like you're making the right choice for your organization then. Our company is considerably smaller and we only build/maintain a single app.
On Tue, Jun 14, 2016 at 11:04 AM, James Smith <j...@sanger.ac.uk> wrote: > We have upwards over 200 people creating content and services - in > differening frameworks, languages ... on the current servers we maintain in > mod_perl the last count we had about 30-40 developers writing perl code > over probably 30 or 40 different applications within the same cluster of > webservers.... > James > > > On 6/14/2016 3:52 PM, John Dunlap wrote: > > Though, if you have no control over what apps you have to support and they > are wirtten in multiple architectures... I can totally see where you're > coming from. > > On Tue, Jun 14, 2016 at 10:48 AM, James Smith <j...@sanger.ac.uk> wrote: > >> We have multiple apps, and we just switch in and out our auth/page >> wrapper/logging/debugging code as we need to, if some one else comes up >> with an app we tell them what they do to get the information and "jobs a >> good-un", much simpler than having multiple embedded >> login/authentication/... methods... We know because other projects use the >> style frameworks you are talking about - and we go you just XYZ, and then >> realize that they are using some nginx/psgi/starman solution and have to go >> - aargh - no you can't just do that - you will have to re-engineer your app! >> >> James >> On 6/14/2016 3:40 PM, John Dunlap wrote: >> >> We don't use any of those hooks into Apache. mod_perl invokes our main >> handler and, from there, we do everything ourselves. We even built our own >> authentication and authorization mechanisms, directly into our application, >> instead of relying on Apache to provide them. We've contained all mod_perl >> specific code to 2-3 files so that we have more freedom to decide how and >> where our application will be deployed. >> >> On Tue, Jun 14, 2016 at 10:37 AM, James Smith < <j...@sanger.ac.uk> >> j...@sanger.ac.uk> wrote: >> >>> >>> On 6/14/2016 3:28 PM, John Dunlap wrote: >>> >>> https://www.nginx.com/blog/nginx-vs-apache-our-view/ >>> >>> Unfortunately for us we actually use some of those 500 things that >>> apache is good at, that nginx doesn't do: >>> >>> - Making use of all the handler/filter hooks in apache; >>> - Fronting a complex web-application, where requests by definition >>> take a long time to return (the databases and related queries are >>> complex) >>> >>> >>> >>> -- The Wellcome Trust 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. >>> >> >> >> >> -- >> John Dunlap >> *CTO | Lariat * >> >> *Direct:* >> * <j...@lariat.co>j...@lariat.co <j...@lariat.co>* >> >> * Customer Service:* >> 877.268.6667 >> <supp...@lariat.co>supp...@lariat.co >> >> >> >> -- The Wellcome Trust 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. >> > > > > -- > John Dunlap > *CTO | Lariat * > > *Direct:* > * <j...@lariat.co>j...@lariat.co <j...@lariat.co>* > > * Customer Service:* > 877.268.6667 > <supp...@lariat.co>supp...@lariat.co > > > > -- The Wellcome Trust 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. > -- John Dunlap *CTO | Lariat * *Direct:* *j...@lariat.co <j...@lariat.co>* *Customer Service:* 877.268.6667 supp...@lariat.co
