<p>Hello,
What are you guys using for load balancers?
I need something that will do only HTTP load balancing.
Fabio looked good until I saw the dependency with consul. </p>
<hr/>**评论：**<br/><br/>bmartensson: <pre><p>I would use nginx or haproxy if its just a simple static LB.
If you need continous deployment, tons of services, rollbacks, etc, look at Kubernetes or Mesos/Marathon. But that requires a bit more work to set up and maintain.</p></pre>andrefsp: <pre><p>Just use nginx. Has been around for a while, its easy to use, its robust and mature. </p></pre>HarveyKandola: <pre><p>Does this help?</p>
<p><a href="https://www.backplane.io" rel="nofollow">https://www.backplane.io</a></p>
<p>I believe it's written in Go.</p></pre>voutasaurus: <pre><p>Backplane is entirely go based. It runs as a service which will save you some big headaches trying to figure out how to distribute your services as you scale. It uses a reverse tunnel to connect your backends to the load balancer so you don't have to worry about firewall configuration. You can run backends on anything that has an internet connection. The open source client used for connection and configuration currently supports linux and OS X. It even supports lossless switchovers (blue/green deploys).</p></pre>OccamsMirror: <pre><p>I wrote my own using a combination of <a href="https://github.com/abh/geodns" rel="nofollow">GeoDNS</a> and <a href="https://github.com/vulcand/oxy" rel="nofollow">Oxy</a></p></pre>FrenchDonkey: <pre><blockquote>
<p>oxy
Oxy looks really good</p>
</blockquote></pre>OccamsMirror: <pre><p>Yeah it is! Very simple to use as well.</p></pre>chub79: <pre><p>I'm using <a href="http://vulcand.github.io/" rel="nofollow">vulcand</a> but it relies on etcd so might not work out for you.</p></pre>Zapadlo: <pre><p>+1 for vulcand</p></pre>FrenchDonkey: <pre><p>Yum... let me see</p></pre>martingx: <pre><p>We're using vulcand too. It's working well. Been in production for a few months.</p></pre>fern4lvarez: <pre><p>You can also use Caddy and its <code>proxy</code> directive, where you can set multiple backends, health checks, routing policy,and more. e.g.:</p>
<pre><code>proxy / web1.local:80 web2.local:90 web3.local:100 {
policy round_robin
health_check /health
proxy_header Host {host}
proxy_header X-Real-IP {remote}
proxy_header X-Forwarded-Proto {scheme}
}
</code></pre>
<p><a href="https://caddyserver.com/docs/proxy" rel="nofollow">https://caddyserver.com/docs/proxy</a></p></pre>chezalfredo: <pre><p>Give a try to <a href="http://traefik.io" rel="nofollow">Traefik </a> :) </p></pre>FrenchDonkey: <pre><p>It looks AWESOME do you have any perf stats ?</p></pre>chezalfredo: <pre><p><a href="http://docs.traefik.io/benchmarks" rel="nofollow">Here</a> :) </p></pre>hayzeus: <pre><p>haproxy works pretty nicely, although the configuration language feels a little awkward until you get used to it.</p>
<p>Bit it's performant and does a LOT. nginx is easier to set up, but not as flexible.</p></pre>
