Apache Aurora vs Kubernetes

Need advice about which tool to choose?Ask the StackShare community!

Apache Aurora

63
82
+ 1
0
Kubernetes

39.1K
33.2K
+ 1
628
Add tool

Apache Aurora vs Kubernetes: 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, Kubernetes is detailed as "Manage a cluster of Linux containers as a single system to accelerate Dev and simplify Ops". Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.

Apache Aurora and Kubernetes are primarily classified as "Cluster Management" and "Container" tools respectively.

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, Kubernetes provides the following key features:

  • Lightweight, simple and accessible
  • Built for a multi-cloud world, public, private or hybrid
  • Highly modular, designed so that all of its components are easily swappable

Apache Aurora and Kubernetes are both open source tools. Kubernetes with 55.1K GitHub stars and 19.1K forks on GitHub appears to be more popular than Apache Aurora with 616 GitHub stars and 231 GitHub forks.

Google, Slack, and Shopify are some of the popular companies that use Kubernetes, whereas Apache Aurora is used by Twitter, Oscar Health, and Chartbeat. Kubernetes has a broader approval, being mentioned in 1047 company stacks & 1096 developers stacks; compared to Apache Aurora, which is listed in 6 company stacks and 3 developer stacks.

Decisions about Apache Aurora and Kubernetes
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 28 upvotes · 3.3M views

Our whole DevOps stack consists of the following tools:

  • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
  • Respectively Git as revision control system
  • SourceTree as Git GUI
  • Visual Studio Code as IDE
  • CircleCI for continuous integration (automatize development process)
  • Prettier / TSLint / ESLint as code linter
  • SonarQube as quality gate
  • Docker as container management (incl. Docker Compose for multi-container application management)
  • VirtualBox for operating system simulation tests
  • Kubernetes as cluster management for docker containers
  • Heroku for deploying in test environments
  • nginx as web server (preferably used as facade server in production environment)
  • SSLMate (using OpenSSL) for certificate management
  • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
  • PostgreSQL as preferred database system
  • Redis as preferred in-memory database/store (great for caching)

The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

  • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
  • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
  • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
  • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
  • Scalability: All-in-one framework for distributed systems.
  • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
See more
Get Advice from developers at your company using Private StackShare. Sign up for Private StackShare.
Learn More
Pros of Apache Aurora
Pros of Kubernetes
    Be the first to leave a pro
    • 159
      Leading docker container management solution
    • 124
      Simple and powerful
    • 101
      Open source
    • 75
      Backed by google
    • 56
      The right abstractions
    • 24
      Scale services
    • 18
      Replication controller
    • 9
      Permission managment
    • 7
      Simple
    • 7
      Supports autoscaling
    • 6
      Cheap
    • 4
      Self-healing
    • 4
      Reliable
    • 4
      No cloud platform lock-in
    • 3
      Open, powerful, stable
    • 3
      Scalable
    • 3
      Quick cloud setup
    • 3
      Promotes modern/good infrascture practice
    • 2
      Backed by Red Hat
    • 2
      Runs on azure
    • 2
      Cloud Agnostic
    • 2
      Custom and extensibility
    • 2
      Captain of Container Ship
    • 2
      A self healing environment with rich metadata
    • 1
      Golang
    • 1
      Easy setup
    • 1
      Everything of CaaS
    • 1
      Sfg
    • 1
      Expandable
    • 1
      Gke

    Sign up to add or upvote prosMake informed product decisions

    Cons of Apache Aurora
    Cons of Kubernetes
      Be the first to leave a con
      • 13
        Poor workflow for development
      • 11
        Steep learning curve
      • 5
        Orchestrates only infrastructure
      • 2
        High resource requirements for on-prem clusters

      Sign up to add or upvote consMake informed product decisions

      What is Apache Aurora?

      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.

      What is Kubernetes?

      Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.

      Need advice about which tool to choose?Ask the StackShare community!

      What companies use Apache Aurora?
      What companies use Kubernetes?
      See which teams inside your own company are using Apache Aurora or Kubernetes.
      Sign up for Private StackShareLearn More

      Sign up to get full access to all the companiesMake informed product decisions

      What tools integrate with Apache Aurora?
      What tools integrate with Kubernetes?

      Sign up to get full access to all the tool integrationsMake informed product decisions

      Blog Posts

      Kubernetesetcd+2
      2
      1027
      Dec 8 2020 at 5:50PM

      DigitalOcean

      GitHubMySQLMongoDB+11
      2
      1864
      PythonDockerKubernetes+7
      3
      697
      May 21 2020 at 12:02AM

      Rancher Labs

      KubernetesAmazon EC2Grafana+12
      3
      1230
      Apr 16 2020 at 5:34AM

      Rancher Labs

      KubernetesRancher+2
      2
      782
      PythonDockerKubernetes+14
      11
      2110
      What are some alternatives to Apache Aurora and Kubernetes?
      Marathon
      Marathon is an Apache Mesos framework for container orchestration. Marathon provides a REST API for starting, stopping, and scaling applications. Marathon is written in Scala and can run in highly-available mode by running multiple copies. The state of running tasks gets stored in the Mesos state abstraction.
      Apache Mesos
      Apache Mesos is a cluster manager that simplifies the complexity of running applications on a shared pool of servers.
      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.
      DC/OS
      Unlike traditional operating systems, DC/OS spans multiple machines within a network, aggregating their resources to maximize utilization by distributed applications.
      YARN Hadoop
      Its fundamental idea is to split up the functionalities of resource management and job scheduling/monitoring into separate daemons. The idea is to have a global ResourceManager (RM) and per-application ApplicationMaster (AM).
      See all alternatives