Merge pull request #55 from OurSQLFoundation/resources/auto-2026-09-24

Add TiDB, Percona XtraDB Cluster, and orchestrator to Software & Tools

Author: Mazizova

content/resources/software/orchestrator/index.md

@@ -0,0 +1,20 @@
+---
+title: "orchestrator"
+link: "https://github.com/percona/orchestrator"
+github: "percona/orchestrator"
+description: "A MySQL replication topology discovery, visualization, and failure-detection tool with a CLI, HTTP API, and web UI, maintained by Percona as a continuation of the original openark/orchestrator project."
+subcategories:
+  - Replication & High Availability
+compatibility:
+  - MySQL
+deployment:
+  - Self-Hosted
+pricing:
+  - Open Source
+images:
+  - logo.png
+---
+
+orchestrator maps out a MySQL replication topology automatically, refreshing it continuously as replicas are added, removed, or re-pointed, and exposes that map through a CLI, an HTTP API, and a web UI so operators can see the full picture of a fleet's replication state at a glance. It detects common failure scenarios and can drive automated recovery and topology refactoring, rather than requiring every change to be scripted and run by hand.
+
+It's released under the Apache 2.0 license. The original project (`openark/orchestrator`) was archived in February 2025; this fork is maintained by Percona, which uses it as the failure-detection and recovery engine inside its Kubernetes Operators for MySQL, and continues to accept fixes.

content/resources/software/orchestrator/logo.png

@@ -0,0 +1,23 @@
+---
+title: "Percona XtraDB Cluster"
+link: "https://github.com/percona/percona-xtradb-cluster"
+github: "percona/percona-xtradb-cluster"
+description: "A synchronous, multi-master MySQL clustering solution built on Galera replication, developed by Percona as a high-availability alternative to standalone MySQL."
+subcategories:
+  - Replication & High Availability
+  - Database Software
+compatibility:
+  - MySQL
+  - Percona Server
+  - Galera
+deployment:
+  - Self-Hosted
+pricing:
+  - Open Source
+images:
+  - logo.png
+---
+
+Percona XtraDB Cluster combines Percona Server for MySQL with Galera replication to provide synchronous, multi-master clustering: writes committed on one node are certified and applied on every other node in the cluster before the transaction returns, so any node can be read from or written to and a node failure doesn't require manual failover. Galera itself is bundled as a submodule of the project rather than an external dependency to install separately.
+
+It's released under the GPLv2 license and developed and maintained by Percona alongside Percona Server for MySQL and Percona XtraBackup, which it uses for state transfers (SST) between cluster nodes.

content/resources/software/percona-xtradb-cluster/index.md

@@ -0,0 +1,23 @@
+---
+title: "TiDB"
+link: "https://github.com/pingcap/tidb"
+github: "pingcap/tidb"
+description: "An open-source, distributed SQL database with MySQL wire-protocol compatibility, built for horizontal scalability, strong consistency, and hybrid transactional/analytical (HTAP) workloads."
+subcategories:
+  - Database Software
+  - Data Warehouse & Analytics
+compatibility:
+  - MySQL
+  - TiDB
+deployment:
+  - Self-Hosted
+  - Kubernetes
+pricing:
+  - Open Source
+images:
+  - logo.png
+---
+
+TiDB is a distributed SQL database developed by PingCAP that speaks the MySQL protocol, so most MySQL clients, drivers, and applications can connect to it with little or no code change while gaining horizontal scale-out, strong (Raft-based) consistency, and built-in high availability across nodes. Its architecture separates the SQL layer from a distributed storage layer, and its TiFlash columnar engine lets the same cluster serve real-time analytical queries alongside transactional traffic without a separate ETL pipeline.
+
+It's released under the Apache 2.0 license and written in Go. Clusters can be run self-managed on bare metal or VMs, or deployed and managed on Kubernetes via the official TiDB Operator; PingCAP also offers a separate fully managed TiDB Cloud service for teams that don't want to run it themselves.