pingcap/tidb

What TiDB Is

TiDB is an open-source, cloud-native distributed SQL database that separates computing from storage. It targets workloads that need horizontal scaling, strong consistency, and high availability without giving up familiar SQL tooling. MySQL 8.0 compatibility means existing drivers, ORMs, and many applications can connect with little or no code change README lines 16–28, and migration utilities are documented in the ecosystem guide data migration tools.

The main capabilities are distributed ACID transactions across nodes, Raft-based replication for automated failover, and HTAP through two storage engines: row-based TiKV and columnar TiFlash, which replicates from TiKV in real time Key Features. Vector search is also listed as an available feature, which makes the database relevant to retrieval-backed applications as well as transactional ones feature overview.

Component Layout

A deployment is not a single process. It consists of SQL front-end nodes, distributed storage (TiKV), a metadata/placement server (PD), and the TiFlash column store. The SQL layer and PD are written in Go, TiKV is written in Rust and uses RocksDB, and TiFlash is C++, according to a PingCAP employee comment on Hacker News component breakdown. The architecture is documented separately with diagrams architecture docs.

Quick Start

The README offers three starting paths depending on what you are evaluating Quick Start:

1. Local test cluster: follow the TiDB quick start guide to deploy a local playground cluster local deployment guide.
2. Kubernetes: use TiDB Operator to deploy in a self-managed cluster or a public-cloud Kubernetes service Kubernetes quick start.
3. TiDB Cloud: start a fully managed cluster from the free plan, no credit card required TiDB Cloud sign-up.

After a cluster is running, connect with a MySQL driver or ORM and follow the application guide Build an App with TiDB. For SQL exploration, the statement overview covers supported syntax SQL statement overview. A browser-based playground is also available for a quick look without installing anything online playground.

Usage Constraints

The README does not give a bare go build-and-run path for the server; quick start is intentionally routed through TiUP, Kubernetes, or TiDB Cloud, so local use assumes you follow those deployment documents. MySQL compatibility is targeted at MySQL 8.0, not every MySQL version or every extension; the compatibility documentation should be consulted before migrating an existing application MySQL compatibility.

The distributed design adds operational surface area: replication, PD, and separate storage engines must be deployed and monitored together. The project is Apache-2.0 licensed, including enterprise-grade features according to the README license. A commenter on Hacker News raised the project's CLA and VC backing as a governance concern, with other commenters arguing that CLAs are normal for commercially supported open source discussion.

HotRepo's take

TiDB appears in the HotRepo Go daily list for 2026-11-06 at rank 8 with 3 stars gained that day, against a total of 40,711 stars and 6,294 forks. The recorded Hacker News threads span 2015, 2017, 2019, and 2025, with the 2025 thread drawing 72 points and 65 comments. That long discussion history is consistent with a mature infrastructure project rather than a new release; the single daily snapshot is not enough to describe a trend. The recurring debate in the 2025 thread is whether teams at ordinary data sizes need a distributed database at all, alongside governance questions about the CLA.