Skip to main content
Load balancers are the traffic directors of your infrastructure — they distribute incoming requests across multiple backend servers, perform health checks to route around failures, and terminate TLS so backend servers don’t need to handle encryption overhead. Hellenic Technologies configures and manages load balancers across cloud-native options (AWS ALB/NLB, GCP Cloud Load Balancing, Azure Application Gateway) and software load balancers (Nginx, HAProxy) depending on the architecture. Nginx is the most versatile option for self-managed infrastructure: it handles HTTP/HTTPS load balancing, serves as a reverse proxy, performs TLS termination, and can implement basic WAF rules via modules. We configure upstream health checks, connection timeouts, and keepalive connection pools for performance. For TCP load balancing and scenarios requiring very high connection throughput, HAProxy is the preferred choice — it handles millions of concurrent connections with minimal resource usage. Sticky sessions (session persistence) are sometimes required for stateful applications that store session data in memory rather than a shared cache. We implement cookie-based session affinity in Nginx and HAProxy, and configure IP hash load balancing as a fallback. However, we always recommend refactoring applications to use Redis-backed sessions instead, which enables true stateless load balancing and makes horizontal scaling straightforward. Load balancing services we configure:
  • Cloud-native load balancer setup: AWS ALB/NLB, GCP CLB, Azure App Gateway
  • Nginx upstream configuration with health checks and failover
  • HAProxy TCP and HTTP load balancing with stats dashboard
  • TLS termination with automatic certificate renewal
  • Sticky session configuration and session persistence policies
  • Weighted load balancing for blue/green and canary deployments
  • Health check configuration: HTTP path, interval, thresholds, and timeout
  • Connection draining for zero-downtime backend replacement
  • Load balancer access log analysis and traffic visualisation
  • Rate limiting and connection limiting at the load balancer layer