Earlier quoted context omitted.
I'd challenge ELB usage in such configuration. R53 should be enough.
It's nice for clean removal of a HAproxy from rotation as well as insulating against HAproxy failures without worrying about DNS caching, not to mention wildly different DNS behavior on different platforms. Some platforms unconditionally use only the first address in a RR A, which is why BIND (and maybe R53) has the "randomize A records" functionality.
NGINX open sources TCP load balancing
81–90 of 121 posts
Re: NGINX open sources TCP load balancing
#82Why would somebody need a TCP load balancer in a web server ? Is there a use-case where the TCP load balancer being with the web-server made a lot of sense ? Integrating too many features into a single software can be risky as it may compromise simplicity and the UNIX way, 1 tool for 1 job..
Re: NGINX open sources TCP load balancing
#83Just a bad title or am I missing something?
Re: NGINX open sources TCP load balancing
#84huh, I thought all of NGINX was open source and so I'm confused by the title "NGINX open sources TCP load balancing." Just a bad title or am I missing something?
Re: NGINX open sources TCP load balancing
#85Re: NGINX open sources TCP load balancing
#86Re: NGINX open sources TCP load balancing
#87Earlier quoted context omitted.
HAProxy offers a better DDos mitigation configurables in comparison to nginx. Thats it.
CloudFlare is build on top of OpenResty which is basically stock nginx with ngx_lua and a bunch of other modules built in. I would argue that if you want it to be, nginx can be much better at DDoS mitigation. You can use the modules limit_conn and limit_req to control how many connection individual IPs can make to your server for basic control.
Re: NGINX open sources TCP load balancing
#88Earlier quoted context omitted.
Not to mention the vast ecosystem of some really great nginx plugins. The one thing I have found desperately wanting in both nginx and haproxy is the support for real-time stats and filtering found in Varnish (supports HTTP only). I am absolutely hooked! // Query Times varnishncsa -F '%t %{VCL_Log:Backend}x %Dμs %bB %s %{Varnish:hitmiss}x "%r"' // Slow Queries varnishncsa -F '%t %{VCL_Log:Backend}x %Dμs %bB %s %{Varn…
I've been able to get real-time stats in nginx by adding custom counters with the lua plugin and exporting a stats handler. http://wiki.nginx.org/HttpLuaModule#ngx.shared.DICT
Re: NGINX open sources TCP load balancing
#89New features should be developed and tested in an open version, so the feedback, testing, patches and even unexpected new improvements from high skilled enthusiasts would be incorporated much more quickly than any closed team with QA (look at the Linux kernel).
We have seen too many examples of "acquiring" open source projects to monetize on its user base (how I hate that idiotic MBA slang) which then became stagnant - from MySQL to Xen, you name it.
I wonder what mr. Sysoev is writing these days?)
Re: NGINX open sources TCP load balancing
#90Earlier quoted context omitted.
It's nice for clean removal of a HAproxy from rotation as well as insulating against HAproxy failures without worrying about DNS caching, not to mention wildly different DNS behavior on different platforms. Some platforms unconditionally use only the first address in a RR A, which is why BIND (and maybe R53) has the "randomize A records" functionality.
ELB isn't magic either. You have to CNAME to it (i.e. mandatory AWS lookup) or use R53. Combine that with ELB slow on-ramp issues on load spikes and the fact that you pay per Gb of traffic passing through and I don't see a benefit. R53 has various advanced synthetic record types as well as healthchecks.