distributed SQL database
TiDB is an open-source, cloud-native distributed SQL database that is MySQL-compatible, supports ACID transactions, horizontal scaling, and HTAP workloads.
Same problem, same approach. Swapping one for another is a config change, not a rewrite.
Production-proven MySQL-compatible distributed SQL database, choose when you want a similarly capable system with Oracle compatibility options.
OceanBase is the unified distributed database for the AI era — open-source, multi-model, one engine for your most demanding workloads.
Solves the same problem with a different architecture or at a different layer. Expect to rewrite the integration.
Cloud-native PostgreSQL-compatible database from Alibaba, choose for PostgreSQL workloads on Alibaba Cloud with separate compute-storage scaling.
A cloud-native database based on PostgreSQL developed by Alibaba Cloud.
Unified HTAP engine with built-in vector search, choose for a Rust-based AI-native database if MySQL compatibility is not critical.
AI-native HTAP database with Git-for-Data and built-in vector search, serving as the data and memory backbone for intelligent agents and applications.
PostgreSQL-compatible distributed SQL database, choose when your stack uses PostgreSQL rather than MySQL.
YugabyteDB - the cloud native distributed SQL database for mission-critical applications.
Distributed PostgreSQL extension, choose when you already run PostgreSQL and want to scale out with sharding instead of a separate database.
Distributed PostgreSQL as an extension
An earlier or more limited way to do the job. Still the right call when you need something small, proven, or CPU-only.
Single-node PostgreSQL with built-in full-text and vector search, choose when you don't need horizontal scaling and prefer the Postgres ecosystem.
One Postgres for your application data, full-text search, vector retrieval, and aggregations. Home of the pg_search extension.
These projects were analysed and named tidb among their alternatives. The relationship is not symmetric — how tidb rates them is a separate judgement, made when tidb is analysed in its own right.
calls tidb “choose when you need a MySQL-compatible distributed SQL database with integrated analytics and vector search.”
CockroachDB — the cloud native, distributed SQL database designed for high availability, effortless scale, and control over data placement.
calls tidb “Choose if you prefer MySQL compatibility, Apache-2.0 licensing, and a proven community for distributed OLTP.”
YugabyteDB - the cloud native distributed SQL database for mission-critical applications.
calls tidb “Same class: mature MySQL-compatible distributed HTAP database; choose for a larger ecosystem and proven scalability.”
OceanBase is the unified distributed database for the AI era — open-source, multi-model, one engine for your most demanding workloads.
calls tidb “A self-contained MySQL-compatible distributed SQL database; choose it when you prefer one integrated engine over managing MySQL shards.”
Vitess is a database clustering system for horizontal scaling of MySQL.
calls tidb “Choose it when you want an actual MySQL-compatible distributed SQL database instead of an external middleware that shards your existing databases.”
Empowering Data Intelligence with Distributed SQL for Sharding, Scalability, and Security Across All Databases.
calls tidb “distributed SQL database with MySQL compatibility; choose for SQL scale with ACID, not multi-model.”
🥑 ArangoDB is a native multi-model database with flexible data models for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.
calls tidb “Choose when you need a MySQL-compatible distributed SQL DB with HTAP and JSON support, outside the Postgres ecosystem.”
Distributed PostgreSQL as an extension
calls tidb “Choose when you need MySQL-wire-compatible distributed SQL with HTAP scale-out instead of an in-process library.”
A simple, fast and versatile Datalog database