Balancers provides implementations of HTTP load-balancers.
Balancers gives you a http.Client from net/http
that rewrites your requests' scheme, host, and userinfo according to the
rules of a balancer. A balancer is simply an algorithm to pick the host for
the next request a http.Client.
Suppose you have a cluster of two servers (on two different URLs) and you want to load balance between them. A very simple implementation can be done with the round-robin scheduling algorithm. Round-robin iterates through the list of available hosts and restarts at the first when the end is reached. Here's some code that illustrates that:
// Get a balancer that performs round-robin scheduling between two servers.
balancer, err := roundrobin.NewBalancerFromURL("https://server1.com", "https://server2.com")
// Get a HTTP client based on that balancer.
client := balancers.NewClient(balancer)
// Now request some data. The scheme, host, and user info will be rewritten
// by the balancer; you'll never get data from http://example.com, only data
// from http://server1.com or http://server2.com.
client.Get("http://example.com/path1?foo=bar") // rewritten to https://server1.com/path1?foo=bar
client.Get("http://example.com/path1?foo=bar") // rewritten to https://server2.com/path1?foo=bar
client.Get("http://example.com/path1?foo=bar") // rewritten to https://server1.com/path1?foo=bar
client.Get("/path1?foo=bar") // rewritten to https://server2.com/path1?foo=barThe current state of Balancers is a proof-of-concept. It didn't touch production systems yet.
Thanks a lot for the great folks working on Go.
MIT-LICENSE. See LICENSE or the LICENSE file provided in the repository for details.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent