[ale] Systemd rants (was bow head)

[agcarver+ale at acarver.net (Alex Carver)]

Funny you bring up that example and configuration.  This article
espouses the "do one thing" concept for each of those applications (even
if accidentally as the author states:

https://arstechnica.com/information-technology/2017/09/how-to-hurricane-proof-a-web-server/



On 2017-09-08 09:04, Adam Jimerson wrote:
> I would say for Nginx to truly fall under the "do one thing and do it well" It 
> would have to lose its proxy support and caching support. This means instead of 
> having Ngnix talk to php-fpm/gunicorn/uwsgi/passenger/etc and it happen to cache 
> things either to disk or RAM to speed things up you would need to have something 
> more like, HAProxy that talks to your php-fpm/gunicorn/uwsgi/passenger/etc and 
> maybe Nginx for any static assets and if you wanted caching you would need to 
> throw in something like Varnish/Memcache. That way each moving wheel is 
> truly only responsible for doing one thing.  That is a very contrived example 
> I'll admit and may actually be dumb to try and deploy which is why Nginx does 
> all the things that it out of the box.
> 
> This is just my view on it and was just meant as an example, not to say that any 
> of this is right or not as at the end of the day we are talking about a 
> philosophy. I'm not against Nginx or Apache for that matter, both tools get the 
> job done although I do prefer Nginx over Apache as I find it nicer to work with.