Difference between revisions of "Load balancer (Networking)"
Jump to navigation
Jump to search
↑ https://docs.nginx.com/nginx/admin-guide/load-balancer/http-load-balancer/#overview
| Line 12: | Line 12: | ||
* [[TCP]], [[UDP]] | * [[TCP]], [[UDP]] | ||
* Load Balancing algorithm: [[WRR]], [[weighted least connection]], [[source IP hash]] | * Load Balancing algorithm: [[WRR]], [[weighted least connection]], [[source IP hash]] | ||
| − | + | * [[Sticky]] [[session]] | |
| − | |||
Revision as of 05:23, 26 March 2020
Load balancing across multiple application instances is a commonly used technique for optimizing resource utilization, maximizing throughput, reducing latency, and ensuring fault‑tolerant configurations.
Load balancing in Nginx is configured using upstream directive.[1]
Network load balancer can provide service for different protocols, such as TCP, UDP, HTTP or HTTPS.
Typical options:
- TCP, UDP
- Load Balancing algorithm: WRR, weighted least connection, source IP hash
- Sticky session
Related terms
See also
- HTTP, HTTP client, HTTP/1.1, HTTP/2, HTTP/3, HTTPS, HSTS CSR, TLS, SSL,
openSSL, WebSockets, WebRTC,ssl_certificateQUIC, HPKP, CT, List of HTTP status codes, URL redirection, Content-type:, Webhook, HTTP headers,--insecure, Axios HTTP client, HTTP cookies, HTTP ETag - Proxy servers:
Squid, Reverse proxy,Nginx,HAProxy,Varnish, Load balancer, Load Balancer as a Service (LBaaS), Symantec proxySG and Advanced Secure Gateway (ASG), Traefik, tinyproxy, Proxyrack, Luminati Networks, SOCKS, Envoy Proxy - Traefik
Advertising:
