4 ms·
There is something that should be said about nginx's third party modules. There are many and they add quite a bit of functionality, especially when they're ups
by drenvuk 8y ago
There is something that should be said about nginx's third party modules. There are many and they add quite a bit of functionality, especially when they're upstream modules.
https://www.nginx.com/resources/wiki/modules/ https://www.nginx.com/resources/wiki/modules/
It's great because you don't even need a web framework, really. If you're comfortable and confident in nginx you can get quite a bit of performance out of the server while adding your application logic to it. I'm not sure why more people don't and just use it as a reverse proxy.
- cagenut 8y agobecause you could do all that and more with apache modules, the reason people switched was because nginx didnt get bogged down in all that. imho its keyword engineering, but you can see given the history why nginx adopters aren't thinking that way.
- eddieroger 8y agoI don't know - I switched from Apache to NGINX because I preferred it's config formatting over writing XML when I stopped using things like CPanel. Many of the NGINX servers under my current role run the NGINX Lua module performing logic on over 1B requests per day. I do try to reduce dependency on modules, but that's not because it makes it too Apache-like, it's for simplicity's sake. If you don't want NGINX to have these features, don't compile it in, then boom. no longer bogged down.
- yjftsjthsd-h 8y agoSeparation of concerns? Might be worth it, but there are tradeoffs in binding everything together.