MySQL vs TurbineProxy

MySQL has no write-up on Specifiction yet; its figures are above.

TurbineProxy is a self-hosted Rust proxy for MySQL and PostgreSQL that directs reads and writes according to query intent, without requiring application code changes. It can route across replicas or run as a standalone proxy in front of one database server. Replica routing supports round-robin or least-connections balancing and excludes replicas when lag exceeds a configured threshold. Per-backend connection pools use multiplexing and configurable sizes. Security controls include SQL injection detection, per-user read-only rules, query allowlists, and AES-256-GCM encryption at rest. For MySQL 8.0 and later, it specifies GTID-aware read-your-own-writes support. A web dashboard, Prometheus metrics, query analytics, a heatmap, and Grafana dashboard JSON cover observability. Its embedded MCP server offers seven tools over JSON-RPC 2.0 with Basic Auth, including slow-query analysis, N+1 detection, index advice, replica lag, and backend health. It is open source under Apache-2.0, with a free plan at free and no per-query fees. Install options include binary, Docker, Homebrew, AUR,.deb, and.rpm.