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.
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
Who uses Apache Aurora?
10 companies reportedly use Apache Aurora in their tech stacks, including Twitter, KAVAK, and Amperity.
56 developers on StackShare have stated that they use Apache Aurora.
Apache Aurora Integrations
Apr 24 2015 at 6:32PM
Apache Aurora's Features
- 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
Apache Aurora Alternatives & Comparisons
What are some alternatives to Apache Aurora?
See all alternatives
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 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 is a cluster manager that simplifies the complexity of running applications on a shared pool of servers.
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.
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).