2 ms·
Fair point, but, > if you want your webserver to do something complex, you'd go for Apache I would tend to disagree. Assuming "complex" = "business logic", Ap
by ag_47 9y ago
Fair point, but,
> if you want your webserver to do something complex, you'd go for Apache
I would tend to disagree. Assuming "complex" = "business logic", Apache hardly seems the right choice. PHP/Python/Node/GoLang or Lua right inside nginx would be more appropriate in most cases, imo.
- smsm42 9y agoThere are degrees of complexity, there's a kind of spectrum even. If you want a full-blown business logic that requires language like PHP or Go, it's insane to try and make Apache do it. If you need a set of simple rules that are within what Apache (including there all the module ecosystem) can and is designed to do, it would be a big mistake, costing a lot of scalability, to deploy high-level language instead. Right tool for the job, always.
- ag_47 9y ago> if you want your webserver to do something complex, you'd go for Apache > a set of simple rules that are within what Apache (including there all the module ecosystem) can and is designed to do
- smsm42 9y agoAgain, there are degrees of complexity. Very simple - nginx, kinda more complex - Apache, somewhat complex but still doable without using Turning-complete language - third-party Apache modules, needs Turing-complete language or you're wasting your time - Python/PHP/Perl/pick your poison.