Load Balancing

Distribute traffic across application servers for high availability, scalability, and fault tolerance.

When to Use

• Distributing HTTP/HTTPS traffic across multiple backend servers.
• Implementing health checks to route around unhealthy instances.
• Terminating TLS at the load balancer for simplified certificate management.
• Enabling blue/green or canary deployments with traffic shifting.
• Scaling horizontally behind a single entry point.

Confirm the exact hosts/account, exposure, maintenance window and rollback before changes. The examples are alternatives with placeholders, not a complete production deployment. Keep stats/admin endpoints private and restrict socket access. /health returning a local static 200 proves only proxy liveness, not backend readiness. Trust forwarded headers only from known proxies and validate client-address handling. Plain HTTP backend hops require an explicit private-network trust model or authenticated TLS.

Prerequisites