OceanBase Database vs ShardingSphere-Proxy

OceanBase Database is a distributed database for transactional, analytical, and AI workloads in one system. Built-in compatibility with Oracle and MySQL is intended to simplify migration. Deployment choices include the open-source Community Edition, self-hosted Enterprise, and fully managed OceanBase Cloud across cloud providers. Documentation describes high availability and disaster recovery at node, data-center, and region levels. Linux installation packages are listed for Alibaba Cloud Linux, CentOS, Red Hat, Ubuntu, Debian, and Anolis OS. Docker deployment can be used on Windows and macOS, though the documentation cautions that this method has not been validated at scale. A standalone instance can be used for learning; production environments require at least three servers. Community Edition is free and includes full kernel capabilities. Enterprise pricing is available on request. Security features include role and permission management, network whitelists, encrypted communication, transparent data encryption, and SQL auditing, but Community Edition does not support security audit.

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.