Orchestrator’s Next Chapter: What It Means for Percona Customers

Why It Matters

Ensuring continuous development of Orchestrator safeguards MySQL HA reliability and protects investments of enterprises relying on the tool.

Key Takeaways

• ProxySQL assumes development of MySQL Orchestrator, reviving the project
• Percona never maintained upstream but will keep supporting customers
• Support for Percona customers remains unchanged after takeover
• Percona Operator for MySQL depends on Orchestrator, prompting coordination
• Community retains Apache 2.0 licensing and a clear roadmap

Pulse Analysis

Orchestrator has been the de‑facto standard for MySQL topology management and automated failover for over a decade. When the original upstream project was archived, many operators were left with stale forks, creating uncertainty around future updates and security patches. ProxySQL’s decision to adopt the codebase and publish a public roadmap restores confidence, ensuring that critical bug fixes and feature enhancements will continue under an active maintainer while preserving the Apache 2.0 license that encourages broad community contributions.

Percona’s response underscores its commitment to customers who rely on Orchestrator as part of their high‑availability stack. Although Percona never served as an upstream maintainer, it has historically offered operational guidance, troubleshooting, and bespoke patches for client deployments. This support model will remain unchanged, meaning enterprises can continue to depend on Percona’s expertise without renegotiating contracts. Moreover, Percona’s own Operator for MySQL incorporates Orchestrator to manage asynchronous replication topologies, making the tool’s health directly relevant to Percona’s product roadmap and reinforcing the need for close collaboration with ProxySQL.

The broader MySQL ecosystem benefits from a revitalized Orchestrator project. Continuous development mitigates the risk of security vulnerabilities and aligns with the growing demand for resilient, cloud‑native database architectures. Operators can expect a clearer upgrade path, improved documentation, and potential new features that address modern deployment patterns such as Kubernetes orchestration. For businesses evaluating HA solutions, the partnership signals stability and a long‑term commitment to open‑source tooling, making Orchestrator a safer choice for mission‑critical workloads.