An open-source, cloud-native, distributed SQL database offering MySQL compatibility, horizontal scalability, and HTAP capabilities.
TiDB is an open-source, cloud-native, distributed SQL database designed for modern applications that require high availability, elastic scalability, and strong consistency. It provides MySQL compatibility, allowing developers to use familiar tools and migrate applications with minimal changes, while offering distributed transactions and hybrid transactional/analytical processing (HTAP) capabilities.
Developers and organizations building scalable, data-intensive applications that need a MySQL-compatible database with horizontal scaling, high availability, and real-time analytics support.
TiDB combines the ease of use of MySQL with the scalability and resilience of a distributed system, offering a seamless path from a single node to a global cluster without sacrificing consistency or performance.
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.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses a two-phase commit protocol to ensure strong consistency across nodes, providing reliability for distributed applications as highlighted in the Key Features.
Separates compute and storage, enabling horizontal and vertical scaling without downtime, allowing growth from a single node to a global cluster.
Leverages Raft consensus for automated failover and data replication, ensuring continuous operation even during node failures.
Combines row-based TiKV and columnar TiFlash engines for real-time analytics on live transactional data without ETL pipelines.
High compatibility with MySQL 8.0 protocols and tools minimizes code changes, supported by data migration tools for easy transition.
Deploying and managing a distributed TiDB cluster, especially via Kubernetes with TiDB Operator, requires significant DevOps skills and infrastructure knowledge.
The distributed architecture introduces latency and resource consumption that may be unnecessary for applications with modest data or query loads.
While MySQL-compatible, some advanced features like certain stored procedures or functions might not be fully implemented, requiring adjustments during migration.
Compared to established databases like PostgreSQL or MySQL, third-party tooling and community support for TiDB are still maturing, which can affect integration ease.