Skip to content

Commit 3f7f1e4

Browse files
committed
Add TiDB, Percona XtraDB Cluster, and orchestrator to Software & Tools
Three MySQL-ecosystem resources not yet in the catalog, sourced from their GitHub repositories (README, license file, and in-repo logo assets): - TiDB (pingcap/tidb) — distributed, MySQL-protocol-compatible SQL database with HTAP support via TiFlash. - Percona XtraDB Cluster (percona/percona-xtradb-cluster) — synchronous multi-master MySQL clustering built on Galera replication. - orchestrator (percona/orchestrator) — MySQL replication topology and failure-detection tool; Percona's maintained continuation of the archived openark/orchestrator project. SaaS & Cloud Solutions and Books & Publications had no qualifying candidates this run — most vendor and publisher sites were unreachable from this session's network, and facts/logos couldn't be verified from a primary source, so no resources were added to those sections rather than risk unverified entries. Verified with `hugo --minify` (0 errors). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MRTDi1j4WSJ8ofnvJm55Be
1 parent cca3a7b commit 3f7f1e4

6 files changed

Lines changed: 66 additions & 0 deletions

File tree

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
title: "orchestrator"
3+
link: "https://github.com/percona/orchestrator"
4+
github: "percona/orchestrator"
5+
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."
6+
subcategories:
7+
- Replication & High Availability
8+
compatibility:
9+
- MySQL
10+
deployment:
11+
- Self-Hosted
12+
pricing:
13+
- Open Source
14+
images:
15+
- logo.png
16+
---
17+
18+
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.
19+
20+
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.
24 KB
Loading
Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
title: "Percona XtraDB Cluster"
3+
link: "https://github.com/percona/percona-xtradb-cluster"
4+
github: "percona/percona-xtradb-cluster"
5+
description: "A synchronous, multi-master MySQL clustering solution built on Galera replication, developed by Percona as a high-availability alternative to standalone MySQL."
6+
subcategories:
7+
- Replication & High Availability
8+
- Database Software
9+
compatibility:
10+
- MySQL
11+
- Percona Server
12+
- Galera
13+
deployment:
14+
- Self-Hosted
15+
pricing:
16+
- Open Source
17+
images:
18+
- logo.png
19+
---
20+
21+
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.
22+
23+
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.
24.3 KB
Loading
Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
title: "TiDB"
3+
link: "https://github.com/pingcap/tidb"
4+
github: "pingcap/tidb"
5+
description: "An open-source, distributed SQL database with MySQL wire-protocol compatibility, built for horizontal scalability, strong consistency, and hybrid transactional/analytical (HTAP) workloads."
6+
subcategories:
7+
- Database Software
8+
- Data Warehouse & Analytics
9+
compatibility:
10+
- MySQL
11+
- TiDB
12+
deployment:
13+
- Self-Hosted
14+
- Kubernetes
15+
pricing:
16+
- Open Source
17+
images:
18+
- logo.png
19+
---
20+
21+
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.
22+
23+
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.
19.2 KB
Loading

0 commit comments

Comments
 (0)