ShardingSphere-Proxy

ShardingSphere-Proxy is a tool that sits between your applications and your databases.

  • Databases
  • Network Services
ShardingSphere-Proxy is a tool that sits between your applications and your databases. It organises data across multiple servers so they act as one powerful system. This allows you to scale up performance, improve security, and manage complex data more easily without changing your existing code.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

70/100 Good

Maintained
100last commit 22 days ago
Popular
8620,817 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
208 GB minimum RAM, runs on ARM

Availability: platform listings confirmed today

GitHub stars
20,817
Open issues
272
Last commit
2026-10-30
Latest release
5.5.3
License
Apache-2.0
Activity
steady

Checked 22 days ago - source: GitHub (apache/shardingsphere)

Resources & Compatibility

Minimum requirements: 8 GB RAM, 200 GB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Start the Proxy from its folder Run `sh bin/start.sh` from the ShardingSphere-Proxy directory to start the service, so the app actually begins accepting connections and using its settings. source
  • Pick a port and settings folder When starting, pass your chosen proxy port and configuration directory (for example, `sh bin/start.sh <proxy_port> <conf_directory>`), so the app uses the settings you edited and avoids port clashes with other services. source
  • CDC: databases and tables must exist If you enable CDC (streaming database changes), make sure the database and table you subscribe to already exist in ShardingSphere-Proxy, otherwise the client has nothing to follow. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I start ShardingSphere-Proxy with a specific port and configuration directory?

Run the start script with the proxy port and configuration directory, for example sh bin/start.sh <proxy_port> <conf_directory>. This makes it use the settings you edited and helps avoid port clashes with other services.

Can I connect to ShardingSphere-Proxy with a third-party database GUI?

ShardingSphere-Proxy can be treated as a MySQL server, so the MySQL command-line tool is recommended. Third-party database tools may produce errors because of certain implementations or options.

What must exist before enabling CDC in ShardingSphere-Proxy?

The database and table you want to subscribe to must already exist in ShardingSphere-Proxy. If they do not exist, the CDC client has nothing to follow.

Answers sourced from shardingsphere.apache.org, shardingsphere.apache.org, shardingsphere.apache.org

Community

Collected 48 days ago - public community threads