Load balancing
lastmod 2024-06-12created 2016-06-0211 edits
Load balancing is a type of computer networking technique that divides work among computer resources such as two or more central processing units or storage devices. This makes it possible to optimize availability and response time. For example, ordinary servers such as IA-32 (a composite configuration) are in a more favorable position in terms of stability than a single mainframe (a single configuration). Load balancing services are provided by suitable hardware and software. This technique is usually used for parallel processing over an internal network (especially high-availability parallel processing).
API Gateways
- Kong API Gateway + comparison of other Gateway solutions (KrakenD, SCG, Tyk, Gloo Edge, APISIX, Ocelot)
- Kong API Gateway (pronounced "kong")
- KrakenD (pronounced "kraken")
- Spring Cloud Gateway
- Tyk (pronounced "tike")
- Gloo Edge (pronounced "glue edge")
- Envoy Proxy
- Apache APISIX
- Ocelot
See also
- HAProxy
- Nginx Web Load Balancer
- GitHub Load Balancer Director (GLB)
- Envoy
- Traefik
- Caddy
- Network Load Balancing (NLB)
- Application Load Balancer (ALB)
- Berkeley Packet Filter (BPF)
Favorite site
Architecture
- Web service architecture for High-Availability and Scalability
- Why you need docker for development (explains L4 load balancing architecture)
- [Recommended] (Translation) Introduction to modern network load balancing and proxying 1
- Round robin, and when RR doesn't solve the problem
- Weighted random & weighted round robin
- Least Connections
- Optimizing for latency
- Peak Exponentially Weighted Moving Average (PEWMA) algorithm
Guide
- [Recommended] Differences between ALB and NLB seen through packet dumps (1) - How ALB works 2
- [Recommended] Differences between ALB and NLB seen through packet dumps (2) - How NLB works 3
References
References
Pages that link here