Alternatives to Apache Aurora logo

Alternatives to Apache Aurora

Kubernetes, Marathon, Apache Mesos, Nomad, and YARN Hadoop are the most popular alternatives and competitors to Apache Aurora.
69
96
+ 1
0

What is Apache Aurora and what are its top alternatives?

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.
Apache Aurora is a tool in the Cluster Management category of a tech stack.
Apache Aurora is an open source tool with GitHub stars and GitHub forks. Here’s a link to Apache Aurora's open source repository on GitHub

Top Alternatives to Apache Aurora

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

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

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

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

  • YARN Hadoop
    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). ...

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

  • kops
    kops

    It helps you create, destroy, upgrade and maintain production-grade, highly available, Kubernetes clusters from the command line. AWS (Amazon Web Services) is currently officially supported, with GCE in beta support , and VMware vSphere in alpha, and other platforms planned. ...

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

Apache Aurora alternatives & related posts

Kubernetes logo

Kubernetes

58.5K
50.3K
677
Manage a cluster of Linux containers as a single system to accelerate Dev and simplify Ops
58.5K
50.3K
+ 1
677
PROS OF KUBERNETES
  • 164
    Leading docker container management solution
  • 128
    Simple and powerful
  • 106
    Open source
  • 76
    Backed by google
  • 58
    The right abstractions
  • 25
    Scale services
  • 20
    Replication controller
  • 11
    Permission managment
  • 9
    Supports autoscaling
  • 8
    Cheap
  • 8
    Simple
  • 6
    Self-healing
  • 5
    No cloud platform lock-in
  • 5
    Promotes modern/good infrascture practice
  • 5
    Open, powerful, stable
  • 5
    Reliable
  • 4
    Scalable
  • 4
    Quick cloud setup
  • 3
    Cloud Agnostic
  • 3
    Captain of Container Ship
  • 3
    A self healing environment with rich metadata
  • 3
    Runs on azure
  • 3
    Backed by Red Hat
  • 3
    Custom and extensibility
  • 2
    Sfg
  • 2
    Gke
  • 2
    Everything of CaaS
  • 2
    Golang
  • 2
    Easy setup
  • 2
    Expandable
CONS OF KUBERNETES
  • 16
    Steep learning curve
  • 15
    Poor workflow for development
  • 8
    Orchestrates only infrastructure
  • 4
    High resource requirements for on-prem clusters
  • 2
    Too heavy for simple systems
  • 1
    Additional vendor lock-in (Docker)
  • 1
    More moving parts to secure
  • 1
    Additional Technology Overhead

related Kubernetes posts

Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 44 upvotes · 9.5M views

How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

https://eng.uber.com/distributed-tracing/

(GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

See more
Yshay Yaacobi

Our first experience with .NET core was when we developed our OSS feature management platform - Tweek (https://github.com/soluto/tweek). We wanted to create a solution that is able to run anywhere (super important for OSS), has excellent performance characteristics and can fit in a multi-container architecture. We decided to implement our rule engine processor in F# , our main service was implemented in C# and other components were built using JavaScript / TypeScript and Go.

Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.

After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...

See more
Marathon logo

Marathon

85
91
5
Deploy and manage containers (including Docker) on top of Apache Mesos at scale
85
91
+ 1
5
PROS OF MARATHON
  • 1
    High Availability
  • 1
    Powerful UI
  • 1
    Service Discovery
  • 1
    Load Balancing
  • 1
    Health Checks
CONS OF MARATHON
    Be the first to leave a con

    related Marathon posts

    Apache Mesos logo

    Apache Mesos

    310
    419
    31
    Develop and run resource-efficient distributed systems
    310
    419
    + 1
    31
    PROS OF APACHE MESOS
    • 21
      Easy scaling
    • 6
      Web UI
    • 2
      Fault-Tolerant
    • 1
      Elastic Distributed System
    • 1
      High-Available
    CONS OF APACHE MESOS
    • 1
      Not for long term
    • 1
      Depends on Zookeeper

    related Apache Mesos posts

    Docker containers on Mesos run their microservices with consistent configurations at scale, along with Aurora for long-running services and cron jobs.

    See more
    Nomad logo

    Nomad

    253
    338
    32
    A cluster manager and scheduler
    253
    338
    + 1
    32
    PROS OF NOMAD
    • 7
      Built in Consul integration
    • 6
      Easy setup
    • 4
      Bult-in Vault integration
    • 3
      Built-in federation support
    • 2
      Self-healing
    • 2
      Autoscaling support
    • 1
      Bult-in Vault inegration
    • 1
      Stable
    • 1
      Simple
    • 1
      Nice ACL
    • 1
      Managable by terraform
    • 1
      Open source
    • 1
      Multiple workload support
    • 1
      Flexible
    CONS OF NOMAD
    • 3
      Easy to start with
    • 1
      HCL language for configuration, an unpopular DSL
    • 1
      Small comunity

    related Nomad posts

    Robert Zuber

    Our backend consists of two major pools of machines. One pool hosts the systems that run our site, manage jobs, and send notifications. These services are deployed within Docker containers orchestrated in Kubernetes. Due to Kubernetes’ ecosystem and toolchain, it was an obvious choice for our fairly statically-defined processes: the rate of change of job types or how many we may need in our internal stack is relatively low.

    The other pool of machines is for running our users’ jobs. Because we cannot dynamically predict demand, what types of jobs our users need to have run, nor the resources required for each of those jobs, we found that Nomad excelled over Kubernetes in this area.

    We’re also using Helm to make it easier to deploy new services into Kubernetes. We create a chart (i.e. package) for each service. This lets us easily roll back new software and gives us an audit trail of what was installed or upgraded.

    See more
    YARN Hadoop logo

    YARN Hadoop

    113
    80
    1
    Resource management and job scheduling technology
    113
    80
    + 1
    1
    PROS OF YARN HADOOP
    • 1
      Batch processing with commodity machine
    CONS OF YARN HADOOP
      Be the first to leave a con

      related YARN Hadoop posts

      DC/OS logo

      DC/OS

      109
      180
      12
      The Datacenter Operating System. The easiest way to run microservices, big data, and containers in production.
      109
      180
      + 1
      12
      PROS OF DC/OS
      • 5
        Easy to setup a HA cluster
      • 3
        Open source
      • 2
        Has templates to install via AWS and Azure
      • 1
        Easy Setup
      • 1
        Easy to get services running and operate them
      CONS OF DC/OS
        Be the first to leave a con

        related DC/OS posts

        kops logo

        kops

        93
        76
        0
        Production Grade K8s Installation, Upgrades, and Management
        93
        76
        + 1
        0
        PROS OF KOPS
          Be the first to leave a pro
          CONS OF KOPS
            Be the first to leave a con

            related kops posts

            Mesosphere logo

            Mesosphere

            80
            108
            6
            Combine your datacenter servers and cloud instances into one shared pool
            80
            108
            + 1
            6
            PROS OF MESOSPHERE
            • 6
              Devops
            CONS OF MESOSPHERE
              Be the first to leave a con

              related Mesosphere posts