AWS ELB (Elastic Load Balancer)


ELB distributes incoming network traffic across multiple servers.
Primary purpose:
Optimize resource use
Enhance application performance
Ensure high availability by preventing any single server from becoming overwhelmed with too many requests.
OSI Model
3 Types of ELB
ELB Type | Protocols | Use Cases | Cost Aspect |
Application Load Balancer (ALB) - Layer 7 | HTTP/HTTPS | Web apps, microservices, content & path-based routing | Costlier |
Network Load Balancer (NLB) - Layer 4 | TCP/UDP/TLS | Low-latency apps, millions of requests/sec, static IP | Moderate |
Gateway Load Balancer (GWLB) - Layer 3 | IP Protocol | Network appliances, firewalls, security monitoring | Less costlier than ALB and NLB |
Load Balancer vs API Gateway vs Kubernetes Ingress (Reverse Proxy)
Feature | Load Balancer | API Gateway | Kubernetes Ingress (Reverse Proxy) |
Primary Purpose | Distributes traffic for high availability | Manages, secures, and scales APIs | Routes external traffic to internal services in Kubernetes |
Layer of Operation | Layer 4 or Layer 7 | Layer 7 | Layer 7 |
Key Features | Traffic distribution, fault tolerance | Authentication, rate limiting, monitoring | URL rewriting, SSL termination, routing |
Use Case | High-traffic web applications (e.g., Amazon) | Microservices architectures (e.g., Netflix) | Containerized apps in Kubernetes (e.g., GitHub) |
API Gateway
API Gateway vs Load Balancer
Example: E-commerce Platform
Load Balancer: Distributes traffic across multiple API Gateway instances.
API Gateway: Manages and secures APIs for product catalog, user authentication, and payment processing.
Kubernetes Ingress: Routes traffic to backend services like inventory management, order processing, and recommendation engines.
Backend Services: Reside in a private subnet and handle the core business logic.
Feel free to share and spread the knowledge! ๐๐ Enjoy Learning! ๐
Subscribe to my newsletter
Read articles from KALPESH MOHANTA directly inside your inbox. Subscribe to the newsletter, and don't miss out.
Written by

KALPESH MOHANTA
KALPESH MOHANTA
๐ Hi there! Welcome to my DevOps adventure! ๐ I'm Kalpesh, a DevOps Engineer, and I'm thrilled to share my journey in the dynamic world of DevOps and Cloud Technologies. ๐ ๐ง Tech Arsenal: CI/CD Automation: Streamlining workflows for seamless deployments. Containers & Orchestration: Docker & Kubernetes. Cloud Platforms: Azure, AWS. Version Control: Git. Configuration Management: YAML, Linux commands. ๐ My Journey: I've had the privilege to work on diverse projects, including a notable deployment for PepsiCo. My expertise spans CI/CD automation, containerization, cloud services, and scripting to enhance system performance and reliability. ๐ก Why Follow Me? Join me as I delve into: Cutting-edge DevOps practices. Automation techniques. Cloud innovations. Tips & tricks for aspiring DevOps professionals. ๐ค Connect & Collaborate: Let's build, learn, and innovate together. Whether you're a fellow tech enthusiast, a professional looking to share insights, or someone eager to learn, let's connect and grow in this vibrant community. ๐ข Follow my LinkedIn & Hashnode blog for insights, tutorials, and updates. Together, we'll embrace the ever-evolving DevOps landscape!