Elastic Load Balancing
Generated by GPT-5-miniExpansion Funnel Raw 93 → Dedup 0 → NER 0 → Enqueued 0
| Elastic Load Balancing | |
|---|---|
 Amazon Web Services LLC · Public domain · source | |
| Name | Elastic Load Balancing |
| Developer | Amazon Web Services |
| Released | 2009 |
Elastic Load Balancing Elastic Load Balancing is a managed Amazon Web Services service that distributes incoming client requests across multiple compute resources to improve application availability and fault tolerance. It integrates with Amazon EC2, Amazon ECS, AWS Lambda, and Amazon EKS while interfacing with Amazon VPC, AWS Identity and Access Management, and AWS CloudWatch for networking, security, and observability. Elastic Load Balancing supports multiple load balancer types and protocols to accommodate web, API, and internal microservice architectures used by enterprises, startups, and research institutions.
Overview
Elastic Load Balancing provides several load balancer types—Application Load Balancer, Network Load Balancer, and Gateway Load Balancer—that target different workload patterns and integrations with Amazon EC2, AWS Fargate, Amazon EKS, and AWS Lambda. It is commonly paired with Amazon RDS, Amazon Aurora, Amazon S3, Amazon DynamoDB, and Amazon CloudFront in distributed application stacks. Organizations such as Netflix (company), Airbnb, Spotify, Dropbox (company), and Slack Technologies exemplify large-scale cloud-native use cases that benefit from managed balancing services. The service aligns with operational practices promoted by DevOps advocates like Martin Fowler, Gene Kim, and Jez Humble.
Architecture and Components
Architecturally, Elastic Load Balancing ties into Amazon VPC networking constructs including subnets and Elastic Network Interfaces, and leverages Elastic IP address management for static endpoints. The Application Load Balancer (ALB) implements HTTP/HTTPS routing, integrating with Let's Encrypt-style certificate management via AWS Certificate Manager and TLS offload for web frameworks like Django, Ruby on Rails, Spring Framework, and Express (web framework). The Network Load Balancer (NLB) operates at Layer 4, supporting volatile TCP and UDP traffic for services such as PostgreSQL, MySQL, Redis, and NATS (software). Gateway Load Balancer enables service chaining with virtual appliances from vendors like Palo Alto Networks, Fortinet, and Cisco Systems. Health checks draw inspiration from practices used in Google Cloud Platform and Microsoft Azure load balancing designs.
Load Balancing Algorithms and Features
Elastic Load Balancing supports routing and distribution modes including round-robin, flow hash, least outstanding requests, and source IP affinity—algorithms conceptually related to techniques described in literature from Van Jacobson and David Patterson. ALB provides advanced HTTP features such as host-based and path-based routing, HTTP/2 and gRPC support, WebSocket handling for frameworks like Socket.IO, and content-based routing used in architectures advocated by Roy Fielding in REST (Representational State Transfer). NLB implements extreme performance and connection-preserving strategies for high-throughput systems used in high-frequency trading and scientific computing clusters at institutions like CERN. Sticky sessions and weighted target groups allow traffic steering for A/B testing strategies popularized by companies like Facebook and Google LLC.
Deployment, Scaling, and High Availability
Deployments of Elastic Load Balancing often span multiple Availability Zones within a given AWS Region to achieve fault isolation and continuity, a pattern recommended in materials from AWS Well-Architected Framework and practitioners at HashiCorp. Auto Scaling groups for Amazon EC2 instances or autoscaling for AWS Fargate tasks are commonly paired to dynamically adjust capacity under load spikes experienced by services like Uber Technologies and Lyft. Blue/green and canary deployment strategies influenced by Kubernetes (software) and Spinnaker (software) are implemented using target group switching and weighted routing. Cross-region architectures combine Elastic Load Balancing with Amazon Route 53 for global failover and resiliency used by enterprises participating in major events like Black Friday sales.
Security and Compliance
Elastic Load Balancing integrates with AWS Identity and Access Management for granular API access controls and with AWS Shield and AWS WAF for distributed denial-of-service mitigation and web application firewalling—controls adopted by finance firms such as Goldman Sachs and health organizations governed by Health Insurance Portability and Accountability Act compliance needs. TLS termination uses certificates provisioned by AWS Certificate Manager and can enforce ciphers and protocols aligned with standards from IETF and guidance from National Institute of Standards and Technology. Network segmentation via Amazon VPC and security groups implements isolation patterns similar to those in PCI DSS-compliant environments used by payment processors like Visa and Mastercard.
Monitoring, Logging, and Troubleshooting
Observability combines Amazon CloudWatch metrics, access logs, and flow logs with distributed tracing systems such as AWS X-Ray, OpenTelemetry, and vendors like Datadog and New Relic. Metrics include request count, latency, HTTP 5xx rates, and target health, which teams at Shopify and Etsy have used to detect regressions. Access logs can be aggregated to Amazon S3 and analyzed with Amazon Athena or ELK stack components like Elasticsearch, Logstash, and Kibana for root-cause analysis. Troubleshooting workflows draw on practices popularized by incident response literature from Google SRE and PagerDuty.
Use Cases and Performance Considerations
Common use cases include web application frontends for companies such as Adobe, API gateways for platforms like Stripe, microservice ingress for architectures influenced by Netflix OSS and Spring Cloud, and VPN/SD-WAN integrations used by enterprises like Siemens. Performance considerations involve balancing latency sensitivity for gaming platforms like Epic Games against throughput needs for media delivery by Hulu and YouTube (service). Capacity planning methodologies reference benchmarks from SPEC and real-world scaling narratives from Twitter and LinkedIn to tune health check intervals, connection idle timeouts, and target group sizes.