[deleted]
We Should Ditch Nginx
41–50 of 176 posts
Re: We Should Ditch Nginx
#42Not relating to the Author's opinion, I would just like to know if there's a legitimate, competent competitor to Nginx apart from Apache? Just curious as I've already had a bad experience with monopolies in the past.
http://cherokee-project.com/ and http://www.lighttpd.net/ are the only other ones I've heard of, and they seem to have their own niche they target. There is also https://github.com/okws/okws. I'm sure there are many more, but none of them have sizable market share, especially compared to nginx/apache.
Re: We Should Ditch Nginx
#43... so write to a named pipe instead of the disk?
Re: We Should Ditch Nginx
#44Not relating to the Author's opinion, I would just like to know if there's a legitimate, competent competitor to Nginx apart from Apache? Just curious as I've already had a bad experience with monopolies in the past.
HAProxy[0] has fit the bill for me in many instances.
Re: We Should Ditch Nginx
#45It's $1350/server per year to pay for the feature. You mention in your post: "Our noble HTTP server". Wait. Not plural? I know that a that is a fair bit of money for a bootstrapped startup, but if you are anticipating enough traffic that the syslog feature is an issue, AND you have at least three floors of offices (as mentioned in your blog post), then maybe your OPEX prioritization is a bit off, and you should just pony up.
Nginx is a great piece of software for $no dollars, maybe it would be good karma to pay for the extras you need?
Re: We Should Ditch Nginx
#46Given the name of the blog (and how it's written), I assume this is meant to be satire?
It is not in terms of the content: "Logging to syslog is available as part of our commercial subscription only." http://nginx.org/en/docs/ngx_core_module.html#error_log
"Satire" doesn't mean "false" or "fake".
Re: We Should Ditch Nginx
#47Earlier quoted context omitted.
This position is without merit. People have every right to say that one particular free option is not what they're looking for, and explain why it's not what they're looking for.
While I agree with your statement on it's face, in the context of the OP, this is just whinging. The author is not just offering constructive criticism on a possible fork of NGINX, he's calling the NGINX business out for "withholding" features. The tone is distinctly one of being "owed" a feature common to another popular FOSS project, instead of being grateful for everything NGINX provides (which is a lot, and proba…
This part of FOSS culture I really dislike as a developer.
Many people seem to consider an offence that other developers need to make a living, instead of being grateful of being able to sell stuff using software they haven't paid a dime for.
Then become outraged when the developers come to the conclusion that the baker won't sell bread for pull requests.
This is what moved me into the direction of suggesting dual license for open source projects, every time someone consults me on it.
Re: We Should Ditch Nginx
#48I do find it a little amusing that the author doesn't want to pay and doesn't want to do it himself.
FOSS is two sided, this is the perfect opportunity to contribute.
FWIW, It's really not that hard to build your own RPM/DEB
Re: We Should Ditch Nginx
#49CloudFlare generates 50gb/s of logs globally and have handled collecting this volume in two ways. Historically the logs are sent to a local syslog-ng through the use of a PIPE and the forwarded to central logger. This can be done with nginx with no patches by just treating the PIPE as file. Just make sure you do a little buffering inside nginx. access_log /dev/nginx_access log_format_name buffer=64k flush=10s; Since…
+1 on that eventual blog post.
Re: We Should Ditch Nginx
#50Earlier quoted context omitted.
You didn't hear what he said, he's specifically not talking about the memory hogging process bases mpm. You seem to think Apache only works that way, but the worker modules are pluggable.
He's talking about Apache MPM Worker which while offering better performance over the traditional Apache MPM Prefork because it's threaded based like NGINX is, it still consumes more RAM than NGINX does, so my point remains...
He's talking about MPM Event¹. It's different from worker and probably not as light as nginx but for most stuff it should compare well.