DBLE vs ShardingSphere-Proxy

DBLE is free, open-source middleware for scaling MySQL through sharding. It uses the MySQL protocol and can replace MySQL in many cases without application code changes. Teams can configure hash, modulo, time-based, range-based, or custom sharding, along with global and ER tables. DBLE lists query routing, connection pooling, load balancing, automatic failover, read/write separation, master-slave expansion, and ZooKeeper cluster deployment. SQL support includes SQL 92 and MySQL dialect features such as joins, unions, grouping, ordering, and distinct queries; some features remain on its roadmap. Query optimization addresses global-table joins, sharded tables, ER relations, and subqueries. Distributed transactions use two-phase commit in normal or XA modes, with XA depending on MySQL 5.7 XA transactions, backend availability, and disk reliability. Security controls include password encryption, IP allowlists, and SQL denylists. Explain plans, MySQL-compatible slow logs, and slow-query reports support operations. DBLE is self-hosted on Linux and GPL-2.0 licensed. The open-source plan costs nothing.

ShardingSphere-Proxy is a self-hosted database proxy that gives clients a database server interface over a binary protocol. Its listed client protocols are MySQL, PostgreSQL, openGauss, and Firebird. It distributes storage and computing across underlying databases through sharding, and provides distributed transactions with a hybrid XA and BASE engine. Read/write splitting balances reads using SQL semantics and awareness of database topology. Other capabilities include migration with sharding, federated queries, transparent encryption, and data masking.

You can deploy it from a binary distribution, as a Docker image, or with Helm. The binary requires Java JRE 8 or higher; Docker needs no additional dependency. For a MySQL backend, the Proxy ext-lib directory needs mysql-connector-j-8.4.0.jar. The project is free at free. Support for system databases and tables such as information_schema and pg_catalog is limited, and some graphical database clients may show errors.