StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. Infrastructure as a Service
  4. Virtualization Platform
  5. AWS Elastic Load Balancing (ELB) vs VMware vSphere

AWS Elastic Load Balancing (ELB) vs VMware vSphere

OverviewComparisonAlternatives

Overview

VMware vSphere
VMware vSphere
Stacks608
Followers550
Votes30
AWS Elastic Load Balancing (ELB)
AWS Elastic Load Balancing (ELB)
Stacks12.8K
Followers8.8K
Votes59

AWS Elastic Load Balancing (ELB) vs VMware vSphere: What are the differences?

# Introduction
This Markdown code compares the key differences between AWS Elastic Load Balancing (ELB) and VMware vSphere in a concise manner.

1. **Implementation**: AWS Elastic Load Balancing (ELB) is a cloud-based service that automatically distributes incoming application traffic across multiple targets, whereas VMware vSphere provides load balancing through dedicated virtual appliances within the data center environment.
2. **Scalability**: ELB is designed to handle dynamic workloads and automatically scales to meet traffic demands, making it well-suited for cloud environments, while VMware vSphere requires manual configuration and scaling of load balancers, limiting its scalability.
3. **Cost Structure**: ELB follows a pay-as-you-go pricing model, where customers are charged based on their usage, while VMware vSphere load balancers require additional licenses and maintenance fees, making them potentially more costly for on-premises deployments.
4. **Integration with Other Services**: ELB seamlessly integrates with other AWS services such as Auto Scaling and Amazon CloudWatch, providing a more holistic cloud solution, whereas VMware vSphere load balancers may require additional configuration to work with third-party services or tools.
5. **Fault Tolerance**: ELB automatically monitors the health of its registered targets and routes traffic only to healthy instances, ensuring high availability and fault tolerance, whereas VMware vSphere load balancers may require manual intervention to redirect traffic in case of failures.
6. **Global Reach**: ELB can be easily deployed across multiple regions worldwide, enabling global load balancing and improving application performance for geographically distributed users, while VMware vSphere load balancing is typically limited to the data center's physical location.

In Summary, AWS Elastic Load Balancing (ELB) is a cloud-native service with automated scalability and integration capabilities, while VMware vSphere load balancing offers more control and customization in on-premises environments.

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.

View Docs
CLI (Node.js)
or
Manual

Detailed Comparison

VMware vSphere
VMware vSphere
AWS Elastic Load Balancing (ELB)
AWS Elastic Load Balancing (ELB)

vSphere is the world’s leading server virtualization platform. Run fewer servers and reduce capital and operating costs using VMware vSphere to build a cloud computing infrastructure.

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.

Powerful Server Virtualization;Network Services;Efficient Storage;Consistent Automation;High Availability;Robust Security
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).
Statistics
Stacks
608
Stacks
12.8K
Followers
550
Followers
8.8K
Votes
30
Votes
59
Pros & Cons
Pros
  • 8
    Strong host isolation
  • 6
    Industry leader
  • 5
    Great VM management (HA,FT,...)
  • 4
    Easy to use
  • 2
    Great Networking
Cons
  • 9
    Price
Pros
  • 48
    Easy
  • 8
    ASG integration
  • 2
    Reliability
  • 1
    Coding
  • 0
    SSL offloading
Integrations
No integrations available
Amazon EC2
Amazon EC2

What are some alternatives to VMware vSphere, AWS Elastic Load Balancing (ELB)?

VirtualBox

VirtualBox

VirtualBox is a powerful x86 and AMD64/Intel64 virtualization product for enterprise as well as home use. Not only is VirtualBox an extremely feature rich, high performance product for enterprise customers, it is also the only professional solution that is freely available as Open Source Software under the terms of the GNU General Public License (GPL) version 2.

HAProxy

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.

Traefik

Traefik

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.

Proxmox VE

Proxmox VE

It is a complete open-source platform for all-inclusive enterprise virtualization that tightly integrates KVM hypervisor and LXC containers, software-defined storage and networking functionality on a single platform, and easily manages high availability clusters and disaster recovery tools with the built-in web management interface.

Fly

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

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.

KVM

KVM

KVM (for Kernel-based Virtual Machine) is a full virtualization solution for Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-V).

Hipache

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.

Qemu

Qemu

When used as a machine emulator, it can run OSes and programs made for one machine (e.g. an ARM board) on a different machine (e.g. your own PC). By using dynamic translation, it achieves very good performance. When used as a virtualizer, it achieves near native performance by executing the guest code directly on the host CPU. it supports virtualization when executing under the Xen hypervisor or using the KVM kernel module in Linux. When using KVM, it can virtualize x86, server and embedded PowerPC, 64-bit POWER, S390, 32-bit and 64-bit ARM, and MIPS guests.

Parallels Desktop

Parallels Desktop

Parallels Desktop for Mac allows you to seamlessly run both Windows and MacOS applications side-by-side with speed, control and confidence.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana