3 ms·
It took me 2 years to finally realize this. Before that, I jumped from one beefed up dedicated server to another just to host few measly, low traffic websites.
by pavs 13y ago
It took me 2 years to finally realize this. Before that, I jumped from one beefed up dedicated server to another just to host few measly, low traffic websites. In my experience, even the most optimized apache installation will not have similar memory footprint as a default nginx install.
I have a question for people who are more proficient in web-servers, what are some of the scenarios where apache is a better choice (feature/speed/stability) than nginx?
- fooyc 13y agoApache has much more features, more modules, supports more auth schemes, etc. And the documentation is awesome. Apache configuration is generally better, less WTF. E.g. the nginx headers module [1] allows you to either set a single header, or an expires directive, but not both. There is a HeadersMoreModule, which is more flexible, but in general nginx configuration looks like that. Aliases/url rewrites/per-dir/per-location configuration are a mess in nginx. Want to set some special directives for the /assets location ? no problem. Want to set special directives for .css files ? no problem. Well, actually if you have .css files in /assets, if will have either directives for /assets or .css, but not both. [1] http://wiki.nginx.org/HttpHeadersModule http://wiki.nginx.org/HttpHeadersModule