I got a 502 when visiting this url, I think it's just irony bmiling at me: http://i.imgur.com/q3n8PpZ.png
NGINX open sources TCP load balancing
21–30 of 121 posts
Re: NGINX open sources TCP load balancing
#22Re: NGINX open sources TCP load balancing
#23The NGINX Plus docs on TCP Load Balancing: http://nginx.com/resources/admin-guide/tcp-load-balancing/ Something to read while we wait for the announcement page to come back up :-)
Re: NGINX open sources TCP load balancing
#24Earlier quoted context omitted.
from what i understand, this could be used for anything tcp related (here[0] they said it could be used to proxy mysql, ldap, rtmp and they use pop3 as an example). i thought haproxy was used basically to proxy http stuff, not general tcp. [0] http://nginx.com/resources/admin-guide/tcp-load-balancing/
You can do tcp loadbalancing with haproxy, you can't do udp though.
Re: NGINX open sources TCP load balancing
#25Earlier quoted context omitted.
HAProxy is used for TCP too. The main benefit from my perspective is that there is one less component in the stack. Whereas I would previously need HAProxy running alongside NGINX to balance TCP and HTTP, I can now do all of this with NGINX.
But why not just use HAProxy? It is often used for plain TCP load balancing (we use it).
I've used HAProxy for a long time and been very happy with it. But, everything else being equal, a stack with n-1 components is better than a stack of n components.
Re: NGINX open sources TCP load balancing
#26Re: NGINX open sources TCP load balancing
#27Re: NGINX open sources TCP load balancing
#28Re: NGINX open sources TCP load balancing
#29Earlier quoted context omitted.
You can do tcp loadbalancing with haproxy, you can't do udp though.
[deleted]
Re: NGINX open sources TCP load balancing
#30Earlier quoted context omitted.
But why not just use HAProxy? It is often used for plain TCP load balancing (we use it).
Because I would still need to run NGINX alongside it to handle HTTP proxying. By removing HAProxy from the stack, I have one less component to manage/maintain/upgrade. I've used HAProxy for a long time and been very happy with it. But, everything else being equal, a stack with n-1 components is better than a stack of n components.