51–60 of 176 posts
Technical workarounds aside, the blog author should get approval from his manager/ceo to purchase commercial nginx. I don't see what's unreasonable about a profitable business paying for a useful commercial feature.
This blog post demonstrates why the syslog feature is ideal for segmenting Nginx's market. Almost nobody cares about it, except the sort of place doing > tens of millions of requests per day. The sort of place that might have some money and the scale to realise that a few thousand bucks is cheaper than a bunch of engineer time. It's a good case study in smart pricing.
In this case, if they kept the same setup, I can see that it would be prohibitively expensive to pay for nginx plus on every single one of those VMs. I'm not sure of the nginx's license terms but if they count VMs as a separate server - probably a no go.
A better solution might be to turn all those VMs into application servers and put a big meaty nginx reverse proxy in front of them; that sounds like it would reduce the nginx bill but could be an awful lot of work. Then again, I presume they have automation, you'd hope so with hundreds of VMs...
My point is that it's likely not quite as simple as a grand a year, which would likely be a no-brainer if it was a site license.
This blog post demonstrates why the syslog feature is ideal for segmenting Nginx's market. Almost nobody cares about it, except the sort of place doing > tens of millions of requests per day. The sort of place that might have some money and the scale to realise that a few thousand bucks is cheaper than a bunch of engineer time. It's a good case study in smart pricing.
This. From the article: >I don’t blame NGINX for wanting money in exchange for what is admittedly amazing software. I just don’t want any part of it. Why not? You're using this awesome software whose value you appreciate and which is, you admit, open source. It's just not convenient enough for you. So why can't you pony up the money for your huge, high-traffic website?
>Yep, they took a feature that Apache httpd has had literally forever and put it behind a pay wall.
Charging for support is one thing, but this seems like it should be a basic feature.
And if I were running a server farm on FOSS software and then realized I'd need to cough up ($1350 * ~100) around $135k for the ability to disable obnoxious behavior, because the corporation arbitrarily decided that this particular feature (that most every other HTTP daemon worth a crap has had for ages) was the one that they're going to require you to pay for, I'd be a bit scandalized too, probably enough to write a blog post about how much it annoyed me.
Not 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.
Conveniently this would support the authors requirements of syslog feature.
I hate when people whinge about free software...... You didn't pay anything for it, you use it to make money yet you whinge.
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.
CloudFlare 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…
This blog post demonstrates why the syslog feature is ideal for segmenting Nginx's market. Almost nobody cares about it, except the sort of place doing > tens of millions of requests per day. The sort of place that might have some money and the scale to realise that a few thousand bucks is cheaper than a bunch of engineer time. It's a good case study in smart pricing.
"NGINX Plus Standard" costs $1,350 annual subscription per server. It sounds like this company has a pretty strange setup, running "hundreds of VMs", presumably all running nginx, and it's the combined impact of those VM logging writes that are so burdening the NetApp devices. In this case, if they kept the same setup, I can see that it would be prohibitively expensive to pay for nginx plus on every single one of tho…
Sigh, another example of the worst thing about OSS - privileged, self-entitled users thinking the world owes them something.
Some people are just jerks. They're the same people who are problem customers for products they pay for too, and probably the same people cutting you off in traffic and not tipping their waiter when they go out to dinner.
Earlier quoted context omitted.
This. From the article: >I don’t blame NGINX for wanting money in exchange for what is admittedly amazing software. I just don’t want any part of it. Why not? You're using this awesome software whose value you appreciate and which is, you admit, open source. It's just not convenient enough for you. So why can't you pony up the money for your huge, high-traffic website?
I can sympathize with this: >Yep, they took a feature that Apache httpd has had literally forever and put it behind a pay wall. Charging for support is one thing, but this seems like it should be a basic feature. And if I were running a server farm on FOSS software and then realized I'd need to cough up ($1350 * ~100) around $135k for the ability to disable obnoxious behavior , because the corporation arbitrarily dec…
CloudFlare 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…
You mean creating a http://linux.die.net/man/7/pipe and configure syslog-ng to read from it?
A very comparable configuration for apache https://peter.blogs.balabit.com/2010/02/how-to-collect-apach...