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

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

ExploreCurated searchesOpen-source alternativesSelf-hosted softwareBlogSitemap
ProjectMCP serverAboutHow we rankPress
LegalPrivacyTerms
© 2026 Bringes Technology SRL·VAT RO45896025·hello@awesome-repositories.com
github avatar

github/orchestratorArchived

0
View on GitHub↗
5,776 stars·952 forks·Go·Apache-2.0·12 views

Orchestrator

Orchestrator is a high availability system and replication manager for MySQL database clusters. It functions as a failover automator and topology visualizer designed to detect master failures and promote standby replicas to minimize system downtime.

The project focuses on managing and reconfiguring MySQL replication topologies to maintain consistent data distribution. It utilizes topology discovery crawling to map replication structures and identifies active failures within the database cluster.

The system provides capabilities for automated cluster recovery, location-aware instance tracking, and constraint-based topology reconfiguration. It also maintains an audit log of state recording to track historical topology changes and failover events.

Features

  • MySQL Replication Failover Tools - Detects master failures and triggers automated promotions based on the state of the MySQL replication graph.
  • Database Replication Topology Discovery - Actively probes database metadata to detect the real-time structure of replication chains and identify broken links.
  • MySQL Topology Visualizers - Provides a real-time visualization of MySQL replication structures to identify failures and map the cluster topology.
  • MySQL Replication Topology Managements - Organizes the replication graph of database clusters to ensure consistent data distribution and availability.
  • MySQL Replication Topology Visualizations - Maps and audits the structure of MySQL replication graphs to identify failures and track instance locations.
  • MySQL High Availability Automations - Automates the failover and recovery of MySQL database clusters to ensure continuous system uptime.
  • Automated Master Failovers - Promotes a standby replica automatically when a master failure occurs to maintain continuous availability.
  • Database Topology Graphs - Builds and displays a directed graph representing the current replication hierarchy and data flow.
  • Database Replication Failure Recoveries - Executes recovery processes to restore a healthy database state after detecting master or intermediate failures.
  • Replication Topology Refactorings - Moves replicas between masters using validation rules to ensure the new configuration is safe.
  • Database Topology Location Tracking - Records the physical location or datacenter of database instances to inform decisions during recovery and replication.
  • Datacenter-Aware Instance Tracking - Associates database nodes with physical datacenters to optimize failover decisions based on geographic proximity.
  • Replication Routing Constraints - Validates the legality of moving replicas between masters using predefined safety and routing rules.
  • Database Tools - MySQL replication topology manager and visualizer.
  • Database Utilities - MySQL replication topology manager with visualization.
  • Chaos Engineering Tools - Manages MySQL replication topology and high availability.

Star history

Star history chart for github/orchestratorStar history chart for github/orchestrator

How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.

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

Frequently asked questions

What does github/orchestrator do?

Orchestrator is a high availability system and replication manager for MySQL database clusters. It functions as a failover automator and topology visualizer designed to detect master failures and promote standby replicas to minimize system downtime.

What are the main features of github/orchestrator?

The main features of github/orchestrator are: MySQL Replication Failover Tools, Database Replication Topology Discovery, MySQL Topology Visualizers, MySQL Replication Topology Managements, MySQL Replication Topology Visualizations, MySQL High Availability Automations, Automated Master Failovers, Database Topology Graphs.

What are some open-source alternatives to github/orchestrator?

Open-source alternatives to github/orchestrator include: openark/orchestrator — MySQL replication topology management and HA. flike/kingshard — Kingshard is a MySQL database proxy and sharding middleware that routes SQL traffic between clients and multiple… 2tvenom/myreplication. andizzle/rwdb — Database wrapper that manage read write connections. codingconcepts/datagen. hexdigest/prep — Prep finds all SQL statements in a Go package and instruments db connection with prepared statements.

Open-source alternatives to Orchestrator

Similar open-source projects, ranked by how many features they share with Orchestrator.
  • openark/orchestratoropenark avatar

    openark/orchestrator

    5,774View on GitHub↗

    MySQL replication topology management and HA

    Go
    View on GitHub↗5,774
  • codingconcepts/datagenC

    codingconcepts/datagen

    0View on GitHub↗
    View on GitHub↗0
  • 2tvenom/myreplication2

    2tvenom/myreplication

    0View on GitHub↗
    View on GitHub↗0
  • andizzle/rwdbandizzle avatar

    andizzle/rwdb

    21View on GitHub↗

    Database wrapper that manage read write connections

    Go
    View on GitHub↗21
See all 30 alternatives to Orchestrator→