AWS Elastic Load Balancing (ELB) vs linkerd: What are the differences?
AWS Elastic Load Balancing (ELB): Automatically distribute your incoming application traffic across multiple Amazon EC2 instances. 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; linkerd: Twitter-Style Operability for Microservices. linkerd is an out-of-process network stack for microservices. It functions as a transparent RPC proxy, handling everything needed to make inter-service RPC safe and sane--including load-balancing, service discovery, instrumentation, and routing.
AWS Elastic Load Balancing (ELB) and linkerd are primarily classified as "Load Balancer / Reverse Proxy" and "Microservices" tools respectively.
Some of the features offered by AWS Elastic Load Balancing (ELB) are:
- 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.
On the other hand, linkerd provides the following key features:
- Adaptive load-balancing
- Fine-grained instrumentation
- Abstractions over service discovery
linkerd is an open source tool with 5K GitHub stars and 499 GitHub forks. Here's a link to linkerd's open source repository on GitHub.
What is AWS Elastic Load Balancing (ELB)?
What is linkerd?
Need advice about which tool to choose?Ask the StackShare community!
What are the cons of using AWS Elastic Load Balancing (ELB)?
What are the cons of using linkerd?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with linkerd?
Sign up to get full access to all the tool integrationsMake informed product decisions
I use an Application Load Balancer to balance the load to the EC2 clusters of nightly.zerotoherojs.com and dojo.zerotoherojs.com.
Addditionally, ELB protects my cluster against DDOS attacks: So it is multi-birds with one stone.
We're progressively migrating from classic ELB to newer ALB for ssl offloading and NLB for internal load balancing.
AWS ELB is used to load balance various web and application services across multiple EC2 instances.
- Application type
- SSL free
- forwarding by rules.
- multiple target groups with only one ALB