MySQL horizontal scaling / distributed database clustering
Vitess is a database clustering system that horizontally scales MySQL by sharding it behind a transparent MySQL-compatible query layer.
Solves the same problem with a different architecture or at a different layer. Expect to rewrite the integration.
A self-contained MySQL-compatible distributed SQL database; choose it when you prefer one integrated engine over managing MySQL shards.
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.
A PostgreSQL-wire distributed SQL database; choose it when you can adopt Postgres compatibility and want built-in multi-region resilience without a MySQL proxy layer.
CockroachDB — the cloud native, distributed SQL database designed for high availability, effortless scale, and control over data placement.
A PostgreSQL extension that shards tables; choose it when you are in the Postgres ecosystem and want scale-out inside an existing engine.
Distributed PostgreSQL as an extension
A PostgreSQL-compatible distributed SQL database; choose it when you want open-source distributed SQL with high availability and geo-distribution rather than a MySQL sharding cluster.
YugabyteDB - the cloud native distributed SQL database for mission-critical applications.
A standalone MySQL-protocol distributed database; choose it when you want one integrated engine instead of Vitess coordinating MySQL shards.
OceanBase is the unified distributed database for the AI era — open-source, multi-model, one engine for your most demanding workloads.
A separate distributed SQL engine with YQL/Postgres compatibility; choose it when you need ACID scale-out and can leave the MySQL toolchain behind.
YDB is an open source Distributed SQL Database that combines high availability and scalability with strong consistency and ACID transactions
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.
Empowering Data Intelligence with Distributed SQL for Sharding, Scalability, and Security Across All Databases.
An earlier or more limited way to do the job. Still the right call when you need something small, proven, or CPU-only.
A lightweight MySQL proxy with sharding and read/write splitting; use it when a simple proxy is enough and you do not need Vitess's full cluster lifecycle and automated resharding.
A high-performance MySQL proxy
These projects were analysed and named vitess among their alternatives. The relationship is not symmetric — how vitess rates them is a separate judgement, made when vitess is analysed in its own right.
calls vitess “Choose Vitess when you are MySQL-only and want a battle-tested proxy/VTgate clustering system managed with a topology service instead of ShardingSphere.”
Empowering Data Intelligence with Distributed SQL for Sharding, Scalability, and Security Across All Databases.
calls vitess “Choose when you need a full MySQL clustering/orchestration platform for horizontal scaling, not a lightweight proxy.”
A high-performance MySQL proxy