Add Prometheus MySQL Server Exporter, go-mysql, and TiDB Operator to Software & Tools

Three GitHub-native MySQL-ecosystem projects not yet in the catalog:
- prometheus/mysqld_exporter — Monitoring & Observability
- go-mysql-org/go-mysql — Connectors & Drivers
- pingcap/tidb-operator — DevOps & Deployment

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Mks9iLEruYnP2HBQiffJEm

Author: claude

content/resources/software/go-mysql/index.md

@@ -0,0 +1,18 @@
+---
+title: "go-mysql"
+link: "https://github.com/go-mysql-org/go-mysql"
+description: "A pure Go library for the MySQL network protocol and replication stream, used to build binlog consumers, MySQL-compatible proxies, and sync tools like canal."
+subcategories:
+  - Connectors & Drivers
+compatibility:
+  - MySQL
+  - MariaDB
+pricing:
+  - Open Source
+images:
+  - logo.png
+---
+
+go-mysql implements the MySQL client/server wire protocol and binary log replication format directly in Go, with no cgo dependency on `libmysqlclient`. It bundles several building blocks on top of that: a lightweight `client` package for issuing queries, a `driver` package that plugs into Go's `database/sql`, a `replication` package for parsing binlog events as a replica would, a `server` package for implementing MySQL-compatible servers and proxies, and the `canal` package for streaming row-level changes into systems like Elasticsearch or Redis.
+
+It's dual-licensed under MIT and BSD-3-Clause (parts of the replication code are adapted from Vitess), and is maintained by the go-mysql-org community as the successor to the original `siddontang/go-mysql` project. It's a common dependency underneath other Go-based MySQL tooling — including CDC and sync utilities — rather than an end-user application on its own.

content/resources/software/go-mysql/logo.png

@@ -0,0 +1,21 @@
+---
+title: "Prometheus MySQL Server Exporter"
+link: "https://github.com/prometheus/mysqld_exporter"
+description: "The official Prometheus exporter for MySQL and MariaDB server metrics — global status and variables, InnoDB engine status, replication state, and Performance Schema data."
+subcategories:
+  - Monitoring & Observability
+compatibility:
+  - MySQL
+  - MariaDB
+deployment:
+  - Self-Hosted
+  - Docker
+pricing:
+  - Open Source
+images:
+  - logo.png
+---
+
+mysqld_exporter connects to a MySQL or MariaDB server with a dedicated, minimally-privileged account (`PROCESS, REPLICATION CLIENT, SELECT`) and exposes its metrics — global status and variables, InnoDB engine status, replication/slave status, and optional Performance Schema and `information_schema` collectors — on an HTTP endpoint that Prometheus can scrape. Individual collectors can be toggled on or off with `--collect.*` flags, and it ships with example Grafana dashboards and Prometheus alerting rules.
+
+It supports MySQL 5.6+ and MariaDB 10.3+, is released under the Apache 2.0 license, and is maintained as an official exporter under the Prometheus GitHub organization. It runs as a standalone binary or as the `prom/mysqld-exporter` Docker image, and is one of the most widely deployed building blocks for MySQL observability stacks that don't use a full commercial monitoring platform.

content/resources/software/mysqld-exporter/index.md

@@ -0,0 +1,19 @@
+---
+title: "TiDB Operator"
+link: "https://github.com/pingcap/tidb-operator"
+description: "The official Kubernetes operator for TiDB — automates deploying, scaling, upgrading, and managing TiDB clusters as cloud-native workloads."
+subcategories:
+  - DevOps & Deployment
+compatibility:
+  - TiDB
+deployment:
+  - Kubernetes
+pricing:
+  - Open Source
+images:
+  - logo.png
+---
+
+TiDB Operator manages the full lifecycle of a TiDB cluster on Kubernetes — provisioning PD, TiKV, and TiDB components, handling rolling upgrades and scaling, automating backup and restore, and integrating with Kubernetes-native monitoring. It's installed via an official Helm chart and is how most self-managed TiDB clusters are run in production rather than deploying the components by hand.
+
+It's developed by PingCAP under the Apache 2.0 license, with documentation available in English and Simplified Chinese. The project's main branch tracks the newer v2 line of the operator, alongside a maintained `release-1.x` branch for the earlier v1 API.