distributed SQL / database sharding middleware
Apache ShardingSphere is a Java database middleware that gives existing heterogeneous databases distributed SQL features (sharding, read/write splitting, data encryption, and transactions) through JDBC or proxy modes.
Same problem, same approach. Swapping one for another is a config change, not a rewrite.
Choose Vitess when you are MySQL-only and want a battle-tested proxy/VTgate clustering system managed with a topology service instead of ShardingSphere.
Vitess is a database clustering system for horizontal scaling of MySQL.
Solves the same problem with a different architecture or at a different layer. Expect to rewrite the integration.
Choose it when you want an actual MySQL-compatible distributed SQL database instead of an external middleware that shards your existing databases.
TiDB is built for agentic workloads that grow unpredictably, with ACID guarantees and native support for transactions, analytics, and vector search. No data silos. No noisy neighbors. No infrastructure ceiling.
Choose it when you want a self-contained distributed SQL database with strong consistency and multi-tenant operation rather than a proxy over SQL databases.
YDB is an open source Distributed SQL Database that combines high availability and scalability with strong consistency and ACID transactions
Choose it when you want a PostgreSQL-compatible distributed SQL database that scales natively instead of routing/sharding a legacy DB setup.
CockroachDB — the cloud native, distributed SQL database designed for high availability, effortless scale, and control over data placement.
Choose it when you are already on PostgreSQL and prefer distributed tables via an in-database extension over an external middleware (note AGPL).
Distributed PostgreSQL as an extension
Choose it when you want a PostgreSQL-compatible distributed SQL database with built-in high availability and no separate gateway layer.
YugabyteDB - the cloud native distributed SQL database for mission-critical applications.
Choose it when you want a multi-model distributed database engine and are willing to migrate off your current databases rather than shard them.
OceanBase is the unified distributed database for the AI era — open-source, multi-model, one engine for your most demanding workloads.
These projects were analysed and named shardingsphere among their alternatives. The relationship is not symmetric — how shardingsphere rates them is a separate judgement, made when shardingsphere is analysed in its own right.
calls shardingsphere “choose when you need to shard existing databases with a middleware layer instead of migrating to a new database.”
CockroachDB — the cloud native, distributed SQL database designed for high availability, effortless scale, and control over data placement.
calls shardingsphere “A Java sharding middleware/proxy layer for MySQL and other databases; choose it when you want DB-agnostic sharding rather than a Kubernetes-native MySQL cluster orchestrator.”
Vitess is a database clustering system for horizontal scaling of MySQL.
calls shardingsphere “Choose when you need to shard existing PostgreSQL/MySQL databases via middleware/proxy rather than a Postgres extension.”
Distributed PostgreSQL as an extension
calls shardingsphere “Choose if you want a middleware layer to shard existing databases without replacing your database.”
YugabyteDB - the cloud native distributed SQL database for mission-critical applications.
calls shardingsphere “Choose it for a broader distributed SQL ecosystem with sharding, scaling, and security, but as a Java proxy, not an EF Core plugin.”
A plugin for Microsoft.EntityFrameworkCore to support repository, unit of work patterns, multiple database with distributed transaction supported, and MySQL multiple databases/tables sharding supported.