blocks|key|2972768|text|haproxy是一个“负载均衡器”，它不知道如何服务文件或动态内容。nginx是一个web服务器，可以做很多有趣的事情。如果你只需要负载均衡%2B+HA某个第三个web服务器，那么haproxy就足够了。如果在第三个服务器上终止请求之前，您需要在路由中实现一些静态内容或一些逻辑，那么您可能需要nginx。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2972769|你可以在同一台主机上看到haproxy%2Bnginx的原因是，它允许你关闭单个nginx实例，而haproxy继续为来自其他主机的请求提供服务。想象一下，有一个使用A记录的RR+DNS：|2972770|myapp.com+IN+A+1.1.1.1
myapp.com+IN+A+1.1.1.2|code-block|syntax|javascript|2972771|其中，1.1.1.1和1.1.1.2是配置了haproxy%2Bnginx的两台主机，用于在它们之间进行负载平衡。现在，由于某些原因，您的1.1.1.1的nginx出现故障。发布到1.1.1.1的浏览器仍然由haproxy提供服务，而haproxy则从1.1.1.2的nginx获取数据。|2972772|希望能有所帮助|2972773|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

haproxy is a "load balancer" it doesn't know to serve files or dynamic content. nginx is a web server capable of many interesting things. if you only need to load balance + HA some third web server then haproxy is enough. if you need to implement some static content or some logic in routing of the requests before terminating them on a third server then you may need nginx.

The reason you can see haproxy+nginx on the same host is that it allows you to bring down single nginx instances while haproxy continues to serve requests from other hosts. Imagine having a RR DNS using A records:

<pre><code>myapp.com IN A 1.1.1.1
myapp.com IN A 1.1.1.2
</code></pre>

where 1.1.1.1 and 1.1.1.2 are two hosts with haproxy+nginx configured to load balance between them. Now for some reason your 1.1.1.1's nginx goes down. The browsers that come to 1.1.1.1 are still being served by haproxy on it which in turn gets data from 1.1.1.2's nginx.

hope it helps

blocks|key|164257|text|HAProxy旁边的NGINX看起来就像特斯拉旁边的2CV…|type|unstyled|depth|inlineStyleRanges|entityRanges|data|164258|Benefits+HAProxy|offset|length|style|BOLD|164259|164260|提供了61个不同指标的综合列表。有关可用的统计数据的完整列表，请参阅第9节。与Nginx的|unordered-list-item|164261|相比，|164262|的状态页更加详细，用户也更友好。它能够轻松地与第三方监控服务(例如Datadog)集成|164263|IPV6、代理协议、透明代理、SSL+&+SNI、HTTP2、API、LUA脚本、RDP连接代理、条形表、多节点会话复制、DDOS和DOS+protection...|164264|。|164265|HAProxy的缺点|164266|164267|不提供Nginx提供的其他功能，如web服务器capabilities|164268|164269|给Nginx带来的好处|164270|164271|由于solution|164272|Useful的功能远不止负载均衡，因此如果您需要负载均衡器和具有高级缓存功能的web服务器，则它是一款功能更强大的|164273|。more+|164274|有一个社区开发的模块，可用于收集比默认|164275|提供的更多的统计信息|164276|缺点Nginx:|164277|164278|仅提供了代表服务器上所有站点的7个统计指标。没有针对每个站点的指标available|164279|The+status页面不友好，也不能提供很多详细信息|164280|非常有限的第三方监控集成possibilities|164281|164282|entityMap^0|0|0|G|0|0|0|0|0|0|0|8|2|0|0|0|Z|0|0|0|B|0|0|0|A|0|0|1L|0|0|6|0|0|J|0|0|A|0|0|8|0|0|0|16|0|0|R|0|0|P|0|0^^$0|@$1|2|3|4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1P|8|@$D|1Q|E|1R|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|1S|8|@]|9|@]|A|$]]|$1|I|3|J|5|K|7|1T|8|@]|9|@]|A|$]]|$1|L|3|M|5|K|7|1U|8|@]|9|@]|A|$]]|$1|N|3|O|5|K|7|1V|8|@]|9|@]|A|$]]|$1|P|3|Q|5|K|7|1W|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1X|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1Y|8|@$D|1Z|E|20|F|G]]|9|@]|A|$]]|$1|V|3|-4|5|6|7|21|8|@]|9|@]|A|$]]|$1|W|3|X|5|K|7|22|8|@$D|23|E|24|F|G]]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|25|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|26|8|@$D|27|E|28|F|G]]|9|@]|A|$]]|$1|11|3|-4|5|6|7|29|8|@]|9|@]|A|$]]|$1|12|3|13|5|K|7|2A|8|@$D|2B|E|2C|F|G]]|9|@]|A|$]]|$1|14|3|15|5|K|7|2D|8|@$D|2E|E|2F|F|G]]|9|@]|A|$]]|$1|16|3|17|5|K|7|2G|8|@$D|2H|E|2I|F|G]]|9|@]|A|$]]|$1|18|3|19|5|K|7|2J|8|@$D|2K|E|2L|F|G]]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|2M|8|@$D|2N|E|2O|F|G]]|9|@]|A|$]]|$1|1C|3|1D|5|6|7|2P|8|@$D|2Q|E|2R|F|G]]|9|@]|A|$]]|$1|1E|3|-4|5|6|7|2S|8|@]|9|@]|A|$]]|$1|1F|3|1G|5|K|7|2T|8|@$D|2U|E|2V|F|G]]|9|@]|A|$]]|$1|1H|3|1I|5|K|7|2W|8|@$D|2X|E|2Y|F|G]]|9|@]|A|$]]|$1|1J|3|1K|5|K|7|2Z|8|@$D|30|E|31|F|G]]|9|@]|A|$]]|$1|1L|3|-4|5|6|7|32|8|@]|9|@]|A|$]]|$1|1M|3|-4|5|6|7|33|8|@]|9|@]|A|$]]]|1N|$]]

NGINX next to HAProxy looks like a 2CV next to a Tesla...

Benefits HAProxy:

<ul>
<li>Provides a comprehensive list of 61 different metrics. See section 9
for a full list of available statistics</li>
<li>The status page is much more detailed and user-friendly as compared to Nginx’s</li>
<li>Easily able to integrate with third-party monitoring services (e.g. Datadog)</li>
<li>IPV6, PROXY PROTOCOL, TRANSPARENT PROXY, SSL &amp; SNI, HTTP2, API, LUA Scripting, RDP connection broker, Stick tables, multi-node session replication, DDOS &amp; DOS protection...</li>
</ul>

Drawbacks HAProxy:

<ul>
<li>Does not provide other features that Nginx offers such as web server capabilities</li>
</ul>

Benefits Nginx:

<ul>
<li>Since Nginx is capable of doing much more than load balancing it is a much more versatile solution</li>
<li>Useful if you require a load balancer as well as a web server with advanced caching ability, and more</li>
<li>There is a community-developed module for greater statistic gathering than what is offered by default</li>
</ul>

Drawbacks Nginx:

<ul>
<li>Only provides 7 stat metrics which represent all sites on the server. There is no individual, per-site metrics available</li>
<li>The status page is not user-friendly nor does it provide many details</li>
<li>Very limited third-party monitoring integration possibilities</li>
</ul>

blocks|key|163114|text|HAProxy绝对是更好的、功能更全的负载均衡器(与免费的nginx相比，而不是nginx+plus+(但也有人会争辩))。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|163115|遗憾的是，HAProxy仍然不能做的一件事是通用的UDP连接。因此，我们在日志lbs上使用了HAProxy和nginx。但是HAProxy在2.3中发布了对syslog/udp的支持，所以我们将要改变这一点。:)|163116|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

HAProxy is definitely the better, more fully featured loadbalancer (compared to the free nginx, not nginx plus (but one could argue that as well).
One thing that HAProxy sadly still can't do is generic UDP connections. So we used HAProxy and nginx on our logging lbs. But HAProxy released support for syslog/udp in 2.3 so we are about to change that. :)

blocks|key|164319|text|我们将HAProxy和nginx一起使用。原因有很多。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|164320|Nginx可以做任何事情(或多或少)，但你不希望你的负载均衡器服务于网页。配置中的一些错误(可能与负载平衡无关)，您的整个设置就会突然停止。假设您有一个Nodejs应用程序、一个Dotnet核心应用程序、由Nginx提供服务的静态文件和一个php应用程序。你只是犯了一些错误，你的4个应用程序就会停滞不前。如果每个应用程序都有多个实例，那么您也失去了冗余。|164321|即使你说Nginx只会做负载均衡，Nginx也不支持代理协议，如果你转发到其他不提供页面服务的服务器，这是有问题的。|164322|此外，做一件事并把它做好也是可以说的。Nginx是当今的主要工具箱。它几乎可以做任何事情。负载均衡器应该是设置中最稳定的部分。难道你不喜欢使用专门为负载平衡而构建的东西吗？|164323|如果你使用清漆，那么HAProxy可以很好地使用它，事实上，它们都是由同一个人制作的。|164324|如果您想要增加一个平衡级别，那么您还可以使用dns作为具有多个HAPROXY实例的负载均衡器。Dns不是为这个perse而设计的，但是你总会有一些薄弱环节。您的负载均衡器也可能崩溃，即使它由您的云提供商管理。如果您的dns条目中有多个服务器，现在大多数web浏览器都会尝试其他服务器，因此它就像一个负载均衡器。您的dns应该非常可靠，从而增加您的正常运行时间。|164325|我们使用2个haproxy实例和2个varnish实例以及两个dns条目。|164326|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

We use HAProxy together with nginx. There are a number of reasons.
Nginx can do everything (more or less) but you don't want your load balancer serving web pages. Some error in config (which might have nothing to do with load balancing) and your entire setup comes to a screeching halt. Imagine that you have a Nodejs app, a Dotnet Core app, static files served by Nginx, and a php app. You just make some mistake and your 4 apps come to a standstill. You have lost your redundancy too if you have multiple instances of each app.
Even if you say that Nginx will only do the load balancing, Nginx doesn't support PROXY Protocol which is problematic if you forward to other servers who are also not serving the pages.
In addition there is something to be said for doing one thing and doing it well. Nginx is the master toolbox today. It does almost everything. Your load balancer is supposed to be the most stable part of your setup. Wouldn't you prefer to use something that was built just for load balancing?
If you use varnish then HAProxy works well with it and in fact they are made by the same people.
If you want an added level of balance then you can also use dns as a load balancer with multiple HAPROXY instances. Dns is not meant for this perse but you will always have some weak link. Your load balancer can crash too even if it's managed by your cloud provider. Most web browsers today will try other servers if there is more than one in your dns entry so it's like a load balancer. Your dns should be very reliable thus increasing your uptime.
We use 2 haproxy instances with 2 varnish instances with two dns entries.

I was looking at using HAProxy and Nginx for load balancing, and I had some questions:

<ul>
<li>Should I use JUST HAProxy over Nginx for the proxy server?</li>
<li>Is there any reason to have HAProxy and Nginx installed on the same proxy server?</li>
</ul>

Thanks

HAProxy vs. Nginx

负载均衡

服务器

路由

我正在考虑使用HAProxy和Nginx进行负载均衡，我有一些问题：我是否应该仅使用HAProxy而不是Nginx作为代理服务器？是否有理由将HAProxy和Nginx安装在同一代理服务器上？谢谢

问HAProxy vs. Nginx
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问HAProxy vs. NginxEN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问HAProxy vs. Nginx
EN