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. Cluster Management
  5. AWS Elastic Load Balancing (ELB) vs Apache Aurora

AWS Elastic Load Balancing (ELB) vs Apache Aurora

OverviewComparisonAlternatives

Overview

Apache Aurora
Apache Aurora
Stacks69
Followers96
Votes0
AWS Elastic Load Balancing (ELB)
AWS Elastic Load Balancing (ELB)
Stacks12.8K
Followers8.8K
Votes59

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

Developers describe Apache Aurora as "An Apcahe Mesos framework for scheduling jobs, originally developed by Twitter". Apache Aurora is a service scheduler that runs on top of Mesos, enabling you to run long-running services that take advantage of Mesos' scalability, fault-tolerance, and resource isolation. On the other hand, AWS Elastic Load Balancing (ELB) is detailed 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.

Apache Aurora can be classified as a tool in the "Cluster Management" category, while AWS Elastic Load Balancing (ELB) is grouped under "Load Balancer / Reverse Proxy".

Some of the features offered by Apache Aurora are:

  • Deployment and scheduling of jobs
  • The abstraction a “job” to bundle and manage Mesos tasks
  • A rich DSL to define services

On the other hand, AWS Elastic Load Balancing (ELB) provides the following key features:

  • 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.

Apache Aurora is an open source tool with 616 GitHub stars and 231 GitHub forks. Here's a link to Apache Aurora's open source repository on GitHub.

Coursera, 9GAG, and Quora are some of the popular companies that use AWS Elastic Load Balancing (ELB), whereas Apache Aurora is used by Twitter, Oscar Health, and Medallia. AWS Elastic Load Balancing (ELB) has a broader approval, being mentioned in 724 company stacks & 316 developers stacks; compared to Apache Aurora, which is listed in 6 company stacks and 3 developer stacks.

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

Apache Aurora
Apache Aurora
AWS Elastic Load Balancing (ELB)
AWS Elastic Load Balancing (ELB)

Apache Aurora is a service scheduler that runs on top of Mesos, enabling you to run long-running services that take advantage of Mesos' scalability, fault-tolerance, and resource isolation.

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.

Deployment and scheduling of jobs;The abstraction a “job” to bundle and manage Mesos tasks;A rich DSL to define services;Health checking;Failure domain diversity;Instant provisioning
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
69
Stacks
12.8K
Followers
96
Followers
8.8K
Votes
0
Votes
59
Pros & Cons
No community feedback yet
Pros
  • 48
    Easy
  • 8
    ASG integration
  • 2
    Reliability
  • 1
    Coding
  • 0
    SSL offloading
Integrations
Apache Mesos
Apache Mesos
Vagrant
Vagrant
Amazon EC2
Amazon EC2

What are some alternatives to Apache Aurora, 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.

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.

Nomad

Nomad

Nomad is a cluster manager, designed for both long lived services and short lived batch processing workloads. Developers use a declarative job specification to submit work, and Nomad ensures constraints are satisfied and resource utilization is optimized by efficient task packing. Nomad supports all major operating systems and virtualized, containerized, or standalone applications.

Apache Mesos

Apache Mesos

Apache Mesos is a cluster manager that simplifies the complexity of running applications on a shared pool of servers.

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.

DC/OS

DC/OS

Unlike traditional operating systems, DC/OS spans multiple machines within a network, aggregating their resources to maximize utilization by distributed applications.

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.

Mesosphere

Mesosphere

Mesosphere offers a layer of software that organizes your machines, VMs, and cloud instances and lets applications draw from a single pool of intelligently- and dynamically-allocated resources, increasing efficiency and reducing operational complexity.

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