awesome-repositories.com
Blog
MCP
awesome-repositories.com

Discover the best open-source repositories with AI-powered search.

ExploreCurated searchesOpen-source alternativesSelf-hosted softwareBlogSitemap
ProjectAboutHow we rankPressMCP server
LegalPrivacyTerms
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
·
Netflix avatar

Netflix/maestro

0
View on GitHub↗
3,794 stars·295 forks·Java·Apache-2.0·16 viewsmaestro-doc.github.io↗

Maestro

Maestro is a distributed job scheduler and containerized data pipeline tool designed to coordinate complex sequences of tasks. It functions as a Kubernetes workflow orchestrator and MLOps automation platform, utilizing directed acyclic graphs to manage task dependencies and execution order across computing clusters.

The system distinguishes itself through the use of isolated container environments for each workflow step, ensuring consistent runtime dependencies. It incorporates an asynchronous event bus to coordinate state transitions and provides lifecycle hook integration that dispatches system events to external endpoints for custom processing and reporting.

The platform covers broad capability areas including data pipeline orchestration, machine learning workflow automation, and real-time pipeline health monitoring. It supports automated execution through cron-based scheduling and maintains fault tolerance for long-running processes via centralized state persistence.

Users can manage the creation, versioning, and triggering of workflow definitions using a provided command-line interface.

Features

  • Data Pipeline Orchestration - Manages complex sequences of data processing tasks by tracking dependencies and execution states across distributed environments.
  • Pipeline Automations - Automates the lifecycle of model training and deployment cycles to ensure consistent machine learning operations.
  • MLOps Platforms - Provides a comprehensive framework for automating the full lifecycle of machine learning model training and deployment.
  • Containerized Pipelines - Provides a solution for scheduling recurring data processing tasks through event-driven triggers and container-based isolation.

AI search

Explore more awesome repositories

Describe what you need in plain English — the AI ranks thousands of curated open-source projects by relevance.

Start searching with AI
  • Job State Persistence - Persists execution state and pipeline progress in a shared database to ensure fault tolerance and recovery for long-running jobs.
  • Containerized Batch Job Schedulers - Triggers and manages isolated container jobs on a recurring schedule to maintain scalable infrastructure.
  • DAG-Based Orchestration - Maps task dependencies into a directed acyclic graph to determine the exact execution order of distributed processes.
  • Distributed Job Schedulers - Coordinates task execution across computing clusters while maintaining state consistency and fault tolerance.
  • Distributed Workflow Orchestrators - Coordinates complex sequences of distributed data and machine learning tasks while managing persistent execution state.
  • Kubernetes Deployments - Executes containerized workflow jobs within Kubernetes clusters to leverage scalable infrastructure for large-scale task processing.
  • Kubernetes Job Orchestration - Executes workflow jobs as isolated containers within a Kubernetes cluster to utilize scalable infrastructure.
  • Distributed Cluster Coordination - Coordinates the deployment and monitoring of containerized tasks across multiple computing clusters.
  • Event Bus Architectures - Implements an asynchronous event bus to coordinate state transitions and task triggers across distributed environments.
  • Directed Acyclic Graph Pipelines - Organizes task execution order using directed acyclic graphs to map dependencies in distributed environments.
  • Container-Based Isolation - Executes individual workflow steps within isolated containers to guarantee consistent runtime dependencies and environment stability.
  • Execution State Persistence - Maintains execution metadata in a shared database to enable fault tolerance and recovery for long-running processes.
  • External System Integrations - Dispatches system events to external endpoints to facilitate custom data processing and reporting outside the core engine.
  • Cron Scheduling - Automates the start of recurring data processing and model training cycles using time-based cron scheduling.
  • Workflow Lifecycle Management - Provides a command-line interface for creating, versioning, and triggering workflow definitions and execution instances.
  • Cron-Based - Uses a cron-based scheduling mechanism to automate the start of recurring data processing and model training cycles.
  • Lifecycle Event Hooks - Extends core workflow logic by dispatching events to external endpoints for custom automation and reporting.
  • Event-Driven Hook Systems - Provides a system for processing system events through message queues to extend functionality and improve visibility of complex loop views.
  • External Service Integrations - Dispatches lifecycle events to external endpoints to enable custom data processing and specialized reporting.
  • Pipeline Health Monitors - Tracks the real-time status and health of automated pipelines to identify failures and ensure reliable task completion.
  • Star history

    Star history chart for netflix/maestroStar history chart for netflix/maestro

    Open-source alternatives to Maestro

    Similar open-source projects, ranked by how many features they share with Maestro.
    • azkaban/azkabanazkaban avatar

      azkaban/azkaban

      4,504View on GitHub↗

      Azkaban is a distributed workflow manager and DAG-based job orchestrator designed as an enterprise batch processor. It serves as a Java-based workflow engine that schedules and executes complex job sequences across a cluster of executor servers, with specific functionality for managing big data workloads on Hadoop clusters. The system distinguishes itself through a distributed executor model that coordinates state via a shared database to ensure high availability. It employs a plugin-based architecture that allows for custom job types and system functionality extensions, including the ability

      Java
      View on GitHub↗4,504
    • mage-ai/mage-aimage-ai avatar

      mage-ai/mage-ai

      8,759View on GitHub↗

      Mage AI is a Python-based data pipeline orchestrator and self-hosted data integrated development environment. It is designed for building, scheduling, and monitoring data workflows using a block-based pipeline design and interactive notebook interface. The platform distinguishes itself by integrating generative AI capabilities, allowing users to connect large language model providers via API to incorporate artificial intelligence into automated data streams. It also functions as an Apache Spark data processor, managing the kernels and infrastructure required for high-volume analytics and larg

      Python
      View on GitHub↗8,759
    • hazelcast/hazelcasthazelcast avatar

      hazelcast/hazelcast

      6,570View on GitHub↗

      Hazelcast is a distributed data platform that combines an in-memory data grid with a stream processing engine to support real-time analytics and event-driven applications. It functions as a partitioned, distributed key-value store that replicates data across cluster nodes to provide low-latency access and high availability. The platform also serves as a distributed SQL query engine, allowing users to execute standard SQL statements against both in-memory datasets and external data sources. What distinguishes Hazelcast is its use of a distributed consensus subsystem to maintain strongly consis

      Javabig-datacachingdata-in-motion
      View on GitHub↗6,570
    • mesos/chronosmesos avatar

      mesos/chronos

      4,376View on GitHub↗

      Chronos is a distributed, fault-tolerant job scheduler designed for managing containerized workloads within a cluster. It functions as a task orchestrator that automates the execution of recurring background jobs and complex, multi-step workflows across distributed computing resources. The system distinguishes itself through its ability to manage directed acyclic graph dependencies, ensuring that tasks are triggered only upon the successful completion of prerequisite jobs. It utilizes a leader-follower consensus architecture to maintain high availability and state persistence, while relying o

      Scalachronoschronos-schedulercron
      View on GitHub↗4,376
    See all 30 alternatives to Maestro→

    Frequently asked questions

    What does netflix/maestro do?

    Maestro is a distributed job scheduler and containerized data pipeline tool designed to coordinate complex sequences of tasks. It functions as a Kubernetes workflow orchestrator and MLOps automation platform, utilizing directed acyclic graphs to manage task dependencies and execution order across computing clusters.

    What are the main features of netflix/maestro?

    The main features of netflix/maestro are: Data Pipeline Orchestration, Pipeline Automations, MLOps Platforms, Containerized Pipelines, Job State Persistence, Containerized Batch Job Schedulers, DAG-Based Orchestration, Distributed Job Schedulers.

    What are some open-source alternatives to netflix/maestro?

    Open-source alternatives to netflix/maestro include: azkaban/azkaban — Azkaban is a distributed workflow manager and DAG-based job orchestrator designed as an enterprise batch processor. It… mage-ai/mage-ai — Mage AI is a Python-based data pipeline orchestrator and self-hosted data integrated development environment. It is… hazelcast/hazelcast — Hazelcast is a distributed data platform that combines an in-memory data grid with a stream processing engine to… mesos/chronos — Chronos is a distributed, fault-tolerant job scheduler designed for managing containerized workloads within a cluster.… apache/storm — Storm is a distributed stream processing framework designed to execute unbounded computations across a cluster to… apache/openwhisk — OpenWhisk is a serverless cloud platform designed for deploying and executing stateless functions in response to API…