AWS Elastic Load Balancing (ELB) vs Weave: What are the differences?
Developers describe AWS Elastic Load Balancing (ELB) as "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. On the other hand, Weave is detailed as "Weave creates a virtual network that connects Docker containers deployed across multiple hosts". Weave can traverse firewalls and operate in partially connected networks. Traffic can be encrypted, allowing hosts to be connected across an untrusted network. With weave you can easily construct applications consisting of multiple containers, running anywhere.
AWS Elastic Load Balancing (ELB) and Weave are primarily classified as "Load Balancer / Reverse Proxy" and "Container" 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, Weave provides the following key features:
- Virtual Ethernet Switch
- Application isolation
"Easy" is the top reason why over 46 developers like AWS Elastic Load Balancing (ELB), while over 2 developers mention "Easy setup" as the leading cause for choosing Weave.
Weave is an open source tool with 5.57K GitHub stars and 517 GitHub forks. Here's a link to Weave's open source repository on GitHub.
According to the StackShare community, AWS Elastic Load Balancing (ELB) has a broader approval, being mentioned in 723 company stacks & 314 developers stacks; compared to Weave, which is listed in 11 company stacks and 4 developer stacks.
Sign up to add or upvote prosMake informed product decisions
Sign up to add or upvote consMake informed product decisions
What is AWS Elastic Load Balancing (ELB)?
What is Weave?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions