Load Balancer
A device or software that distributes incoming network traffic across multiple backend servers. Load balancers improve availability, reliability, and performance by ensuring no single server is overwhelmed. They can operate at Layer 4 (TCP) or Layer 7 (HTTP). A misconfigured load balancer can cause 502 Bad Gateway or 503 Service Unavailable errors.
Protocolos relacionados
Mencionado em guias
HTTP Proxy Headers: X-Forwarded-For, Via, and Forwarded
HTTP Fundamentals
API Versioning Strategies: URI, Header, and Query
API Design & Best Practices
Debugging Timeout Errors: 408 and 504
Debugging & Troubleshooting
Debugging 503 Service Unavailable Errors in Production
Debugging & Troubleshooting
Debugging Connection Reset Errors
Debugging & Troubleshooting
Debugging WebSocket Disconnections
Debugging & Troubleshooting
Debugging Redirect Loops (ERR_TOO_MANY_REDIRECTS)
Debugging & Troubleshooting
DNS Record Types Explained: A, AAAA, CNAME, MX, TXT, and Beyond
DNS & Networking
WebSocket Close Codes: Why Your Connection Dropped
Real-Time Protocols
WebRTC Signaling with SIP and WebSocket
Real-Time Protocols
Health Check Endpoint Design Guide
Error Handling Patterns
Connection Management and Keep-Alive
Performance & Optimization
Load Balancing Strategies for APIs
Performance & Optimization
WebSocket Performance Tuning
Performance & Optimization
Connection Pooling for HTTP Clients: Best Practices and Pitfalls
Performance & Optimization
RFC 9114: HTTP/3 Protocol Deep Dive
Protocol Deep Dives
Migrating from HTTP/1.1 to HTTP/2
Migration & Upgrades
Migrating from HTTP/2 to HTTP/3: QUIC Deployment Guide
Migration & Upgrades
Migrating from WebSocket to Server-Sent Events
Migration & Upgrades
Load Balancer Health Checks: HTTP, TCP, and gRPC Probes
Production Infrastructure
Zero-Downtime Deployments: Blue-Green, Canary, and Rolling Updates
Production Infrastructure
TLS Termination: Where to Terminate HTTPS and Why
Production Infrastructure
Connection Draining: Graceful Shutdown Without Dropping Requests
Production Infrastructure
Request ID and Distributed Tracing: Correlating Logs Across Services
Production Infrastructure
Custom Error Pages: 404, 500, 502, and Maintenance Pages
Production Infrastructure
API Gateway Patterns: Architecture and Use Cases
API Gateway Patterns
Cenários relacionados
502 Bad Gateway in Nginx Reverse Proxy
HTTP
503 Service Unavailable During Traffic Spikes
HTTP
504 Gateway Timeout — Upstream Not Responding
HTTP
502 Bad Gateway — WebSocket Upgrade Failure Through Proxy
HTTP
gRPC UNAVAILABLE — Connection Failures
gRPC
1013 Try Again Later — Server Overloaded
WebSocket
503 Service Unavailable — SIP Trunk Overloaded
SIP
486 Busy Here — Call Routing Loop Misdiagnosis
SIP
Definido em
Veja também
Status Code
HTTP Concepts
API Gateway
API Design
Reverse Proxy
Networking
Health Check
Error Handling
Ingress Controller
Infrastructure
Service Discovery
Infrastructure
Load Balancing Algorithm
Infrastructure
Blue-Green Deployment
Infrastructure
Health Check Endpoint
Infrastructure
Layer 4 Load Balancing
Load Balancing & Proxying
Sticky Sessions (Session Affinity)
Load Balancing & Proxying
HAProxy
Load Balancing & Proxying
SSL Offloading
Load Balancing & Proxying
Backend Pool
Load Balancing & Proxying