Add sysbench, dbdeployer, and WeScale to Software & Tools

Three real, actively maintained MySQL-ecosystem tools not yet in the
catalog: sysbench (the standard OLTP/sysbench-style benchmark tool),
dbdeployer (local MySQL/MariaDB/Percona/Galera sandbox deployer, now
maintained by the ProxySQL team), and WeScale (a Vitess-fork database
proxy from ApeCloud with read-write splitting and declarative DDL).

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

Author: claude

content/resources/software/dbdeployer.md

@@ -0,0 +1,21 @@
+---
+title: "dbdeployer"
+link: "https://github.com/ProxySQL/dbdeployer"
+description: "Deploys single, replicated, or Galera MySQL/MariaDB/Percona Server sandboxes locally in seconds, for development and testing — no root access or Docker required."
+subcategories:
+  - Testing & Benchmarking
+  - DevOps & Deployment
+compatibility:
+  - MySQL
+  - MariaDB
+  - Percona Server
+  - Galera
+deployment:
+  - Self-Hosted
+pricing:
+  - Open Source
+---
+
+dbdeployer unpacks a MySQL, MariaDB, or Percona Server tarball and spins up single instances, master/replica replication topologies, Group Replication, Galera/PXC clusters, or InnoDB Cluster — each one isolated in its own directory with its own ports, so multiple versions and flavors can run side by side on one machine. It's a Go rewrite of the older Perl-based MySQL-Sandbox, built by Giuseppe Maxia.
+
+The project is now maintained by the ProxySQL team (with Maxia's blessing), with CI that tracks compatibility across MySQL 5.6 through 9.5, MariaDB 10.11/11.8, and Percona Server/PXC 8.0 and 8.4, including ProxySQL-fronted deployments. It's released under the Apache 2.0 license.

content/resources/software/sysbench.md

@@ -0,0 +1,17 @@
+---
+title: "sysbench"
+link: "https://github.com/akopytov/sysbench"
+description: "A scriptable, multi-threaded benchmark tool based on LuaJIT — the de facto standard for OLTP-style load testing and CPU/memory/file-IO benchmarking of MySQL servers."
+subcategories:
+  - Testing & Benchmarking
+compatibility:
+  - MySQL
+deployment:
+  - Self-Hosted
+pricing:
+  - Open Source
+---
+
+sysbench bundles a set of `oltp_*.lua` workloads that drive realistic transactional load against a MySQL server, alongside standalone CPU, memory, thread-scheduler, and file-IO benchmarks that don't need a database at all. It reports throughput and latency percentiles/histograms and can sustain hundreds of millions of tracked events with low overhead, and new workloads can be written as plain Lua scripts.
+
+Written by Alexey Kopytov and released under the GPL-2.0 license, it's distributed as binary packages for Debian/Ubuntu, RHEL/CentOS, Fedora, and Arch Linux via packagecloud, plus Homebrew on macOS. It's one of the most widely used tools for MySQL hardware sizing, configuration tuning, and regression testing.

content/resources/software/wescale.md

@@ -0,0 +1,19 @@
+---
+title: "WeScale"
+link: "https://github.com/wesql/wescale"
+description: "An open-source MySQL database proxy forked from Vitess — adds transparent read-write splitting, non-blocking declarative DDL, and connection scaling for application developers."
+subcategories:
+  - Proxies & Traffic Management
+compatibility:
+  - MySQL
+deployment:
+  - Self-Hosted
+  - Docker
+  - Kubernetes
+pricing:
+  - Open Source
+---
+
+WeScale sits between an application and MySQL to take on cross-cutting concerns that don't belong in the database itself: routing reads to replicas and writes to the primary, running schema changes as non-blocking declarative DDL, and scaling up the number of logical client connections a single MySQL instance can serve. It ships with a Prometheus/Grafana dashboard for monitoring the proxy and the cluster behind it.
+
+Built by ApeCloud as a fork of the Vitess project, it targets a simpler single-proxy deployment model aimed at application developers, rather than the full sharded-topology setup Vitess is usually run with. It's written in Go, tested against MySQL 5.7 and 8.0, and released under the Apache 2.0 license; it can be run directly, via Docker, or deployed to Kubernetes through the KubeBlocks operator.