Open-Awesome
CategoriesAlternativesStacksSelf-HostedExplore
Open-Awesome

© 2026 Open-Awesome. Curated for the developer elite.

TermsPrivacyAboutGitHubRSS
  1. Home
  2. Cassandra
  3. Peloton

Peloton

Apache-2.0Go

A unified resource scheduler for co-scheduling batch, stateless, and stateful workloads in a single cluster to maximize resource utilization.

GitHubGitHub
647 stars64 forks0 contributors

What is Peloton?

Peloton is a unified resource scheduler that co-schedules mixed workloads—such as batch, stateless, and stateful jobs—in a single compute cluster. It solves the problem of low resource utilization in large-scale environments by enabling elastic resource sharing, overcommitment, and workload preemption. Designed for web-scale operations, it handles millions of containers and tens of thousands of nodes efficiently.

Target Audience

Platform engineers, SREs, and infrastructure teams at web-scale companies managing large, heterogeneous clusters with diverse workload types. It is particularly relevant for organizations running big data and machine learning workloads alongside traditional services.

Value Proposition

Developers choose Peloton for its ability to maximize cluster utilization through advanced features like hierarchical resource pools, GPU/gang scheduling, and cloud-agnostic deployment. Its scalability and support for mixed workloads make it a robust alternative to simpler schedulers in complex, high-demand environments.

Overview

Unified Resource Scheduler to co-schedule mixed types of workloads such as batch, stateless and stateful jobs in a single cluster for better resource utilization.

Use Cases

Best For

  • Managing large-scale clusters with millions of containers
  • Co-scheduling batch, stateless, and stateful workloads together
  • Improving resource utilization in heterogeneous compute environments
  • Running GPU-intensive machine learning jobs like TensorFlow with gang scheduling
  • Implementing hierarchical resource sharing across multiple teams
  • Deploying a cloud-agnostic scheduler for on-premise or cloud datacenters

Not Ideal For

  • Small to medium-sized clusters with under a thousand nodes, where complexity outweighs benefits
  • Teams already standardized on Kubernetes seeking seamless container orchestration without Mesos integration
  • Organizations lacking dedicated infrastructure teams to manage dependencies like Zookeeper and Cassandra
  • Projects requiring quick, out-of-the-box scheduling with minimal configuration and setup time

Pros & Cons

Pros

Elastic Resource Sharing

Uses hierarchical resource pools to dynamically allocate resources among teams, enabling better utilization in large clusters as highlighted in the README's feature list.

Advanced ML Optimization

Supports GPU and gang scheduling for TensorFlow and dynamic resource allocation for Spark, making it ideal for big data and machine learning workloads, per the README's optimization features.

High Scalability

Designed to scale to millions of containers and tens of thousands of nodes, proven in web-scale environments like Uber, as stated in the README's scalability claims.

Cloud-Agnostic Flexibility

Can run in on-premise datacenters or public clouds, providing deployment versatility without vendor lock-in, emphasized in the project philosophy.

Cons

Complex Architecture

Requires managing four separate daemons and dependencies on Zookeeper for service discovery and Mesos for resource abstraction, increasing operational overhead and setup complexity.

Steep Operational Learning Curve

Demands expertise in distributed systems and specific components like Cassandra for storage, which may deter teams without dedicated infrastructure resources.

Limited Ecosystem and Community

Built on Mesos with a niche focus, Peloton has a smaller community and tooling compared to more popular schedulers like Kubernetes, potentially limiting support and integrations.

Frequently Asked Questions

Quick Stats

Stars647
Forks64
Contributors0
Open Issues13
Last commit3 years ago
CreatedSince 2017

Tags

#container-orchestration#batch-processing#stateful-workloads#big-data#mesos#machine-learning#cluster-management

Built With

M
Mesos
g
gRPC
C
Cassandra
Z
Zookeeper
P
Protobuf

Included in

Cassandra316
Auto-fetched 1 day ago

Related Projects

ZipkinZipkin

Zipkin is a distributed tracing system

Stars17,469
Forks3,095
Last commit2 months ago
Netflix: StaashNetflix: Staash

A language-agnostic as well as storage-agnostic web interface for storing data into persistent storage systems, the metadata layer abstracts a lot of storage details and the pattern automation APIs take care of automating common data access patterns.

Stars213
Forks39
Last commit10 years ago
JanuesGraph-UtilsJanuesGraph-Utils

Develop a graph database app using JanusGraph

Stars208
Forks92
Last commit7 years ago
SSTable ToolsSSTable Tools

Tools for parsing, creating and doing other fun stuff with sstables

Stars164
Forks32
Last commit9 years ago
Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a projectStar on GitHub