<div dir="ltr">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/<span style="color:rgb(33,33,33)">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 </span>php-fpm/<font color="#212121">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.</font><div><div><font color="#212121"><br></font></div><div><font color="#212121">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. </font><span style="color:rgb(33,33,33)">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.</span></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, Sep 8, 2017 at 11:37 AM Kyle Brieden <<a href="mailto:kyle@txmoose.com">kyle@txmoose.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I would argue that Nginx is MUCH closer to the "Do one thing" philosophy<br>
than apache is. Nginx essentially only serves up static content and<br>
caches some of that static content in memory to serve it faster. I<br>
think that falls well within the "do one thing" of serving static<br>
content. Nginx doesn't do any server side processing at all; you need<br>
php-fpm for php, gunicorn/uwsgi for python, etc... Nginx passes the<br>
request back to those, those do the processing and hand rendered pages<br>
to nginx, and as far as nginx is concerned, that's a static asset that<br>
it fires out the front. All HTML/CSS/JS assets that it serves are<br>
static content, rendered in browser. One could argue that nginx isn't a<br>
"webserver" at all, although that's what it made it's name on. It<br>
basically only does proxy to other things that do processing and then<br>
serves up static objects.<br>
<br>
On that same token, the fact that it can loadbalance and have many<br>
backends to proxy to falls well within the purview of "being good at<br>
proxying".<br>
<br>
Just my 2 cents.<br>
<br>
---<br>
Very respectfully,<br>
Kyle Brieden<br>
<br>
On 08-09-2017 10:01, Adam Jimerson wrote:<br>
>> Thanks for the reminder for why I don't use either Emacs or Apache.<br>
><br>
> Sorry but that is a pretty week statement unless you use something<br>
> that can only edit text/hex/whatever your working with files and/or<br>
> only using a web server only capable of service static files (html,<br>
> css, js, misc files, etc)/a dedicated proxy server/a dedicated caching<br>
> server.<br>
><br>
> Nginx even violates the "Do one thing and do it well" as it is a web<br>
> server that works well as forward/reverse proxy and it has really good<br>
> caching support. Same for some of the smaller more obscure web<br>
> servers like lighttpd and Caddy to name a few.<br>
><br>
> On Fri, Sep 8, 2017 at 9:25 AM DJ-Pfulio <<a href="mailto:DJPfulio@jdpfu.com" target="_blank">DJPfulio@jdpfu.com</a>> wrote:<br>
><br>
>> Thanks for the reminder for why I don't use either Emacs or Apache.<br>
>><br>
>> On 09/08/2017 07:58 AM, Jim Kinney wrote:<br>
>>> UNIX is dead. Linux isn't UNIX. It's only UNIX-like.<br>
>>><br>
>>> Emacs violates those rules. An editor that can read your email out<br>
>> loud<br>
>>> is rather crossing domains.<br>
>>><br>
>>> Apache violates those rules. The proxy capabilities are beyond<br>
>> it's<br>
>>> initial web server domain.<br>
>>><br>
>>> But at least systemd provides a topic other than vi vs emacs to<br>
>> squabble<br>
>>> over. That was getting old.<br>
>>><br>
>>> Besides, systemd follows most of the rules that were listed about<br>
>> as<br>
>>> well as any other PID 1 process responsible for a current system<br>
>> startup.<br>
>>><br>
>>> On September 8, 2017 7:28:45 AM EDT, Jerald Sheets<br>
>> <<a href="mailto:questy@gmail.com" target="_blank">questy@gmail.com</a>> wrote:<br>
>>><br>
>>> I avoid all the BS and just hate it for its design, layout,<br>
>> and<br>
>>> intrusion into all sorts of things it shouldn’t be fiddling<br>
>> around<br>
>>> in, breaking a myriad of tenets of the “UNIX way”.<br>
>>><br>
>>> The “UNIX Way” is to have a tool that does one thing, does<br>
>> it very<br>
>>> well, has clearly defined input and output and doesn’t try<br>
>> to handle<br>
>>> multiple responsibility domains.<br>
>>><br>
>>> "This is the Unix philosophy: Write programs that do one thing<br>
>> and<br>
>>> do it well. Write programs to work together. Write programs to<br>
>>> handle text streams, because that is a universal interface.”<br>
>> — Doug<br>
>>> McIlroy, the inventor of UNIX pipes<br>
>>><br>
>>><br>
>>> This is why grep doesn’t awk and vice-versa. In case<br>
>> we’ve forgotten:<br>
>>><br>
>>> The Rule of Modularity:<br>
>>> Write simple parts connected by clean interfaces.<br>
>>> Rule of Clarity:<br>
>>> Clarity is better than cleverness.<br>
>>> Rule of Composition:<br>
>>> Design programs to be connected with other programs.<br>
>>> Rule of Separation:<br>
>>> Separate policy from mechanism; separate interfaces from<br>
>> engines.<br>
>>> Rule of Simplicity:<br>
>>> Design for simplicity; add complexity only where you must.<br>
>>> Rule of Parsimony:<br>
>>> Write a big program only when it is clear by demonstration<br>
>> that<br>
>>> nothing else will do.<br>
>>> Rule of Transparency:<br>
>>> Design for visibility to make inspection and debugging easier.<br>
>>> Rule of Robustness:<br>
>>> Robustness is the child of transparency and simplicity.<br>
>>> Rule of Representation:<br>
>>> Fold knowledge into data, so program logic can be stupid and<br>
>> robust.<br>
>>> Rule of Least Surprise:<br>
>>> In interface design, always do the least surprising thing.<br>
>>> Rule of Silence:<br>
>>> When a program has nothing surprising to say, it should say<br>
>> nothing.<br>
>>> Rule of Repair:<br>
>>> Repair what you can — but when you must fail, fail noisily<br>
>> and as<br>
>>> soon as possible.<br>
>>> Rule of Economy:<br>
>>> Programmer time is expensive; conserve it in preference to<br>
>> machine time.<br>
>>> Rule of Generation:<br>
>>> Avoid hand-hacking; write programs to write programs when you<br>
>> can.<br>
>>> Rule of Optimization:<br>
>>> Prototype before polishing, Get it working before you optimize<br>
>> it.<br>
>>> Rule of Diversity:<br>
>>> Distrust all claims for one true way.<br>
>>> Rule of Extensibility:<br>
>>> Design for the future, because it will be here sooner than you<br>
>> think.<br>
>>><br>
>>><br>
>>> I’ll stick with what has worked extremely well for almost 50<br>
>> years.<br>
>>><br>
>>><br>
>>><br>
>>> —jms<br>
>>><br>
>>><br>
>>>> On Sep 8, 2017, at 3:10 AM, Steve Litt<br>
>> <<a href="mailto:slitt@troubleshooters.com" target="_blank">slitt@troubleshooters.com</a><br>
>>>> <mailto:<a href="mailto:slitt@troubleshooters.com" target="_blank">slitt@troubleshooters.com</a>>> wrote:<br>
>>>><br>
>>>> On Thu, 7 Sep 2017 12:29:46 +0000<br>
>>>> "Lightner, Jeffrey" <<a href="mailto:JLightner@dsservices.com" target="_blank">JLightner@dsservices.com</a><br>
>>>> <mailto:<a href="mailto:JLightner@dsservices.com" target="_blank">JLightner@dsservices.com</a>>> wrote:<br>
>>>><br>
>>>>> Caveman conversation:<br>
>>>>> Ug: What that?<br>
>>>>> Zog: Wheel.<br>
>>>>> Ug: Why wheel? Drag work for years.<br>
>>>>> Zog: More fast to use wheel.<br>
>>>>> Ug: Wheel made by false god to trap draggers. It bad.<br>
>>>>> Ug then clubs Zog because Zog doesn't see the intrinsic<br>
>> "reason" of<br>
>>>>> Ug's opinion.<br>
>>>>><br>
>>>>><br>
>>>>> Move ahead 10,000 years:<br>
>>>>> Ug: What that?<br>
>>>>> Zog: Systemd.<br>
>>>>> Ug: Why systemd. Init work for years...<br>
>>>>><br>
>><br>
>> _______________________________________________<br>
>> Ale mailing list<br>
>> <a href="mailto:Ale@ale.org" target="_blank">Ale@ale.org</a><br>
>> <a href="http://mail.ale.org/mailman/listinfo/ale" rel="noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
>> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
>> <a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
> _______________________________________________<br>
> Ale mailing list<br>
> <a href="mailto:Ale@ale.org" target="_blank">Ale@ale.org</a><br>
> <a href="http://mail.ale.org/mailman/listinfo/ale" rel="noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
> <a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo</a>_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org" target="_blank">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" rel="noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</blockquote></div>