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. Utilities
  3. API Tools
  4. Service Discovery
  5. AWS Elastic Load Balancing (ELB) vs Eureka

AWS Elastic Load Balancing (ELB) vs Eureka

OverviewComparisonAlternatives

Overview

Eureka
Eureka
Stacks291
Followers779
Votes70
GitHub Stars12.7K
Forks3.8K
AWS Elastic Load Balancing (ELB)
AWS Elastic Load Balancing (ELB)
Stacks12.8K
Followers8.8K
Votes59

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

Introduction

AWS Elastic Load Balancing (ELB) and Eureka are two widely used load balancing services. While both help distribute traffic across multiple resources, there are key differences between them.

  1. Scalability:

    • ELB: Elastic Load Balancing is a highly scalable service provided by AWS. It automatically scales up or down based on the incoming traffic, ensuring optimal performance.
    • Eureka: Eureka is an open-source load balancing solution used by Netflix. It is also designed to be scalable, allowing for the addition or removal of instances dynamically.
  2. Integration:

    • ELB: Being an AWS service, ELB seamlessly integrates with other AWS services, such as Amazon EC2 and Auto Scaling, making it easier to manage the entire infrastructure.
    • Eureka: Eureka is commonly used in conjunction with Spring Cloud, making it a great choice for applications built with Java and Spring.
  3. Health Checking:

    • ELB: AWS ELB performs automatic health checks on the registered instances, ensuring that only healthy instances receive traffic. It monitors the health of the instances and distributes traffic accordingly.
    • Eureka: Eureka includes a built-in health check mechanism, allowing it to verify the availability and health of registered instances. It marks instances as UP or DOWN based on health checks.
  4. Load Balancer Algorithms:

    • ELB: AWS ELB offers multiple load balancing algorithms, including round-robin, least connections, and IP-based affinity. These algorithms distribute traffic evenly across the available instances.
    • Eureka: Eureka uses the round-robin algorithm by default. However, it can be easily customized to use other load balancing algorithms as well.
  5. Service Discovery:

    • ELB: Elastic Load Balancing focuses primarily on load balancing and does not offer full-fledged service discovery features. It can distribute traffic to instances, but it does not provide comprehensive service registry and lookup capabilities.
    • Eureka: Eureka, on the other hand, provides robust service discovery functionalities. It offers service registration and lookup, allowing clients to dynamically discover and communicate with different services.
  6. Pricing and Licensing:

    • ELB: AWS ELB is a managed service provided by Amazon Web Services. It follows the pay-as-you-go pricing model, where you pay based on the number of hours and data processed by the load balancer.
    • Eureka: Eureka is an open-source solution, making it free to use. However, it requires hosting and managing the Eureka server infrastructure, which may incur costs.

In Summary, AWS Elastic Load Balancing (ELB) is a scalable load balancing service provided by AWS, integrating well with other AWS services, while Eureka is an open-source load balancing solution commonly used with Spring Cloud, offering service discovery capabilities.

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

Eureka
Eureka
AWS Elastic Load Balancing (ELB)
AWS Elastic Load Balancing (ELB)

Eureka is a REST (Representational State Transfer) based service that is primarily used in the AWS cloud for locating services for the purpose of load balancing and failover of middle-tier servers.

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.

-
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
GitHub Stars
12.7K
GitHub Stars
-
GitHub Forks
3.8K
GitHub Forks
-
Stacks
291
Stacks
12.8K
Followers
779
Followers
8.8K
Votes
70
Votes
59
Pros & Cons
Pros
  • 21
    Easy setup and integration with spring-cloud
  • 9
    Web ui
  • 8
    Health checking
  • 8
    Monitoring
  • 7
    Circuit breaker
Cons
  • 1
    Nada
Pros
  • 48
    Easy
  • 8
    ASG integration
  • 2
    Reliability
  • 1
    Coding
  • 0
    SSL offloading
Integrations
Amazon EC2
Amazon EC2
Amazon EC2
Amazon EC2

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

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.

Consul

Consul

Consul is a tool for service discovery and configuration. Consul is distributed, highly available, and extremely scalable.

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.

Zookeeper

Zookeeper

A centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. All of these kinds of services are used in some form or another by distributed applications.

etcd

etcd

etcd is a distributed key value store that provides a reliable way to store data across a cluster of machines. It’s open-source and available on GitHub. etcd gracefully handles master elections during network partitions and will tolerate machine failure, including the master.

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.

Keepalived

Keepalived

The main goal of this project is to provide simple and robust facilities for loadbalancing and high-availability to Linux system and Linux based infrastructures.

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.

node-http-proxy

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.

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