What are the main features of openark/orchestrator?

The main features of openark/orchestrator are: Topology Refactoring Interfaces, Database Replication Topology Discovery, MySQL Replication Topology Managements, MySQL Replication Topology Managers, Replication Topology Refactorings, MySQL Replication CLI and API Interfaces, CLI and Web GUI Operation Interfaces, Replication Topology Recovery Orchestrations.

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

Open-source alternatives to openark/orchestrator include: github/orchestrator — Orchestrator is a high availability system and replication manager for MySQL database clusters. It functions as a… rqlite/rqlite — rqlite is a distributed relational database that replicates SQLite data across a cluster using the Raft consensus… erikgrinaker/toydb — ToyDB is a distributed SQL database that provides a system for storing and querying data across multiple nodes. It… lni/dragonboat — Dragonboat is a Go implementation of the Raft consensus protocol designed to maintain consistent state across a… hashicorp/raft — This is a Raft consensus library and distributed consensus engine implemented in Go. It provides the primitives… hashicorp/nomad — Nomad is a distributed workload orchestrator and infrastructure automation platform designed to manage the lifecycle…

Orchestrator

MySQL replication topology management and HA

Features

Topology Refactoring Interfaces - Provides a drag-and-drop visual interface for safe MySQL replication topology refactoring.
Database Replication Topology Discovery - Crawls MySQL replication topologies to map servers, replication status, and configuration for visual diagrams.
MySQL Replication Topology Managements - Manages and visualizes MySQL replication topologies with automated discovery and safe refactoring of replica relationships.
MySQL Replication Topology Managers - Manages and visualizes MySQL replication topologies with automated discovery and safe refactoring of replica relationships.
Replication Topology Refactorings - Moves replicas between masters safely using drag-and-drop or CLI commands while rejecting illegal refactoring attempts.
MySQL Replication CLI and API Interfaces - Offers command-line and HTTP API access for scripting MySQL replication topology management and recovery operations.
CLI and Web GUI Operation Interfaces - Controls topology management and recovery operations through CLI, HTTP API, and web interface.
Replication Topology Recovery Orchestrations - Automates failover by evaluating replication rules and dependencies before promoting a new master.
MySQL High Availability Controllers - Detects MySQL master failures and orchestrates automatic or manual recovery using topology-aware state evaluation.
MySQL High Availability Automations - Automatically detects MySQL master failures and orchestrates topology-aware recovery to maintain database availability.
MySQL Failover Orchestrations - Controls MySQL failover workflows through CLI, API, and web interfaces with topology-aware state evaluation.
MySQL Replication Failover Tools - Handles MySQL master and intermediate master failovers with configurable recovery policies and manual override support.
Database Topology Graphs - Renders interactive graphs of MySQL replication topologies for real-time monitoring and manual topology changes.
Raft Consensus Implementations - Uses the Raft protocol to coordinate leader election and maintain consistent state across orchestrator nodes.
Topology-Based Failure Detections - Compares current server states against expected topology patterns to identify master and intermediate master failures.
REST and CLI Dual Interfaces - Exposes all topology management and recovery operations through both a RESTful API and a command-line interface.
Database Replication Failure Recoveries - Detects master and intermediate master failures and recovers automatically or manually using topology state.
Database Topology Polling - Periodically crawls MySQL servers to build and refresh a live graph of replication relationships.
MySQL Topology Visualizers - Provides a web interface for drag-and-drop MySQL replication topology refactoring and real-time cluster visualization.
MySQL Replication Topology Visualizations - Maps and displays MySQL replication topologies including server status, replication configuration, and hierarchical relationships.
Replication Topology Graph Renderings - Renders the discovered MySQL replication topology as an interactive graph for real-time monitoring.
Replication and Migration - Manages replication topology and high availability.
Database Tools - MySQL replication topology manager and visualizer.

Star history

openarkorchestratorArchived

Name: openark/orchestrator
Author: openark

View on GitHub

5,774 stars951 forksGoApache-2.04 views

Orchestrator

MySQL replication topology management and HA

Features

Topology Refactoring Interfaces - Provides a drag-and-drop visual interface for safe MySQL replication topology refactoring.
Database Replication Topology Discovery - Crawls MySQL replication topologies to map servers, replication status, and configuration for visual diagrams.
MySQL Replication Topology Managements - Manages and visualizes MySQL replication topologies with automated discovery and safe refactoring of replica relationships.
MySQL Replication Topology Managers - Manages and visualizes MySQL replication topologies with automated discovery and safe refactoring of replica relationships.
Replication Topology Refactorings - Moves replicas between masters safely using drag-and-drop or CLI commands while rejecting illegal refactoring attempts.
MySQL Replication CLI and API Interfaces - Offers command-line and HTTP API access for scripting MySQL replication topology management and recovery operations.
CLI and Web GUI Operation Interfaces - Controls topology management and recovery operations through CLI, HTTP API, and web interface.
Replication Topology Recovery Orchestrations - Automates failover by evaluating replication rules and dependencies before promoting a new master.
MySQL High Availability Controllers - Detects MySQL master failures and orchestrates automatic or manual recovery using topology-aware state evaluation.
MySQL High Availability Automations - Automatically detects MySQL master failures and orchestrates topology-aware recovery to maintain database availability.
MySQL Failover Orchestrations - Controls MySQL failover workflows through CLI, API, and web interfaces with topology-aware state evaluation.
MySQL Replication Failover Tools - Handles MySQL master and intermediate master failovers with configurable recovery policies and manual override support.
Database Topology Graphs - Renders interactive graphs of MySQL replication topologies for real-time monitoring and manual topology changes.
Raft Consensus Implementations - Uses the Raft protocol to coordinate leader election and maintain consistent state across orchestrator nodes.
Topology-Based Failure Detections - Compares current server states against expected topology patterns to identify master and intermediate master failures.
REST and CLI Dual Interfaces - Exposes all topology management and recovery operations through both a RESTful API and a command-line interface.
Database Replication Failure Recoveries - Detects master and intermediate master failures and recovers automatically or manually using topology state.
Database Topology Polling - Periodically crawls MySQL servers to build and refresh a live graph of replication relationships.
MySQL Topology Visualizers - Provides a web interface for drag-and-drop MySQL replication topology refactoring and real-time cluster visualization.
MySQL Replication Topology Visualizations - Maps and displays MySQL replication topologies including server status, replication configuration, and hierarchical relationships.
Replication Topology Graph Renderings - Renders the discovered MySQL replication topology as an interactive graph for real-time monitoring.
Replication and Migration - Manages replication topology and high availability.
Database Tools - MySQL replication topology manager and visualizer.

Open-source alternatives to Orchestrator

Similar open-source projects, ranked by how many features they share with Orchestrator.

github/orchestrator
github/orchestrator
5,776View on GitHub
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
Go
View on GitHub5,776
hashicorp/raft
hashicorp/raft
9,037View on GitHub
This is a Raft consensus library and distributed consensus engine implemented in Go. It provides the primitives necessary to build fault-tolerant distributed services by implementing a replicated state machine that ensures a group of servers agree on a shared system state through leader election and log replication. The project distinguishes itself through a pluggable architecture for storage backends and snapshot storage, decoupling the consensus logic from physical persistence. It includes specialized mechanisms for leadership transfer, protocol version management to support rolling upgrade
Go
View on GitHub9,037
erikgrinaker/toydb
erikgrinaker/toydb
7,251View on GitHub
ToyDB is a distributed SQL database that provides a system for storing and querying data across multiple nodes. It focuses on maintaining strong consistency and fault tolerance through the implementation of a distributed consensus algorithm. The project distinguishes itself by supporting historical data versioning, enabling time-travel queries to retrieve the state of the database from a specific point in the past. It utilizes multi-version concurrency control to manage ACID transactions and ensure data integrity during concurrent operations. The system covers relational data modeling with t
Rust
View on GitHub7,251
lni/dragonboat
lni/dragonboat
5,308View on GitHub
Dragonboat is a Go implementation of the Raft consensus protocol designed to maintain consistent state across a distributed cluster of nodes. It provides a library for building distributed state machines that ensure data integrity and fault tolerance during system failures. The project distinguishes itself through a multi-group Raft implementation, which partitions data across independent consensus groups to distribute workloads and increase overall system processing capacity. It also incorporates mutual TLS to encrypt inter-node communication and verify the identity of cluster members. The
Goconsensusdistributed-consensusdistributed-storage
View on GitHub5,308

See all 30 alternatives to Orchestrator

Frequently asked questions

What does openark/orchestrator do?