AWS Elastic Load Balancing (ELB) vs Traefik
Overview
Share your Stack
Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.
CLI (Node.js)
Manual
Detailed Comparison
With Elastic Load Balancing, you can add and remove EC2 instances as your needs change without disrupting the overall flow of information. If one EC2 instance fails, Elastic Load Balancing automatically reroutes the traffic to the remaining running EC2 instances. If the failed EC2 instance is restored, Elastic Load Balancing restores the traffic to that instance. Elastic Load Balancing offers clients a single point of contact, and it can also serve as the first line of defense against attacks on your network. You can offload the work of encryption and decryption to Elastic Load Balancing, so your servers can focus on their main task. | A modern HTTP reverse proxy and load balancer that makes deploying microservices easy. Traefik integrates with your existing infrastructure components and configures itself automatically and dynamically. |
Distribution of requests to Amazon EC2 instances (servers) in multiple Availability Zones so that the risk of overloading one single instance is minimized. And if an entire Availability Zone goes offline, Elastic Load Balancing routes traffic to instances in other Availability Zones.;Continuous monitoring of the health of Amazon EC2 instances registered with the load balancer so that requests are sent only to the healthy instances. If an instance becomes unhealthy, Elastic Load Balancing stops sending traffic to that instance and spreads the load across the remaining healthy instances.;Support for end-to-end traffic encryption on those networks that use secure (HTTPS/SSL) connections.;The ability to take over the encryption and decryption work from the Amazon EC2 instances, and manage it centrally on the load balancer.;Support for the sticky session feature, which is the ability to "stick" user sessions to specific Amazon EC2 instances.;Association of the load balancer with your domain name. Because the load balancer is the only computer that is exposed to the Internet, you don’t have to create and manage public domain names for the instances that the load balancer manages. You can point the instance's domain records at the load balancer instead and scale as needed (either adding or removing capacity) without having to update the records with each scaling activity.;When used in an Amazon Virtual Private Cloud (Amazon VPC), support for creation and management of security groups associated with your load balancer to provide additional networking and security options.;Supports use of both the Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6). | Continuously updates its configuration (No restarts!);
Supports multiple load balancing algorithms;
Provides HTTPS to your microservices by leveraging Let's Encrypt (wildcard certificates support);
Circuit breakers, retry;
High Availability with cluster mode;
See the magic through its clean web UI;
Websocket, HTTP/2, GRPC ready;
Provides metrics;
Keeps access logs;
Fast;
Exposes a Rest API |
Statistics | |
Stacks 12.8K | Stacks 965 |
Followers 8.8K | Followers 1.2K |
Votes 59 | Votes 93 |
Pros & Cons | |
Pros
| Pros
Cons
|
Integrations | |
What are some alternatives to AWS Elastic Load Balancing (ELB), Traefik?
HAProxy
HAProxy (High Availability Proxy) is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications.
Fly
Deploy apps through our global load balancer with minimal shenanigans. All Fly-enabled applications get free SSL certificates, accept traffic through our global network of datacenters, and encrypt all traffic from visitors through to application servers.
Envoy
Originally built at Lyft, Envoy is a high performance C++ distributed proxy designed for single services and applications, as well as a communication bus and “universal data plane” designed for large microservice “service mesh” architectures.
Hipache
Hipache is a distributed proxy designed to route high volumes of http and websocket traffic to unusually large numbers of virtual hosts, in a highly dynamic topology where backends are added and removed several times per second. It is particularly well-suited for PaaS (platform-as-a-service) and other environments that are both business-critical and multi-tenant.
node-http-proxy
node-http-proxy is an HTTP programmable proxying library that supports websockets. It is suitable for implementing components such as proxies and load balancers.
Modern DDoS Protection & Edge Security Platform
Protect and accelerate your apps with Trafficmind’s global edge — DDoS defense, WAF, API security, CDN/DNS, 99.99% uptime and 24/7 expert team.
DigitalOcean Load Balancer
Load Balancers are a highly available, fully-managed service that work right out of the box and can be deployed as fast as a Droplet. Load Balancers distribute incoming traffic across your infrastructure to increase your application's availability.
F5 BIG-IP
It ensures that applications are always secure and perform the way they should. You get built-in security, traffic management, and performance application services, whether your applications live in a private data center or in the cloud.
Google Cloud Load Balancing
You can scale your applications on Google Compute Engine from zero to full-throttle with it, with no pre-warming needed. You can distribute your load-balanced compute resources in single or multiple regions, close to your users and to meet your high availability requirements.
GLBC
It is a GCE L7 load balancer controller that manages external loadbalancers configured through the Kubernetes Ingress API.
