pingcap/tidb

TiDB is built for agentic workloads that grow unpredictably, with ACID guarantees and native support for transactions, analytics, and vector search. No data...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 26 minutes ago
Added to GitGenius on July 6th, 2024
Created on September 6th, 2015
Open Issues & Pull Requests: 6,829 (+2)
Number of forks: 6,229
Total Stargazers: 40,464 (+0)
Total Subscribers: 1,207 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 29.4 hours
Mean response time: 209.5 days
90th percentile: 900.2 days
Tracked items: 5,138

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 72% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "affects-8.5" is answered fastest, typically in about 3 hours, while "affects-7.1" waits about 3 days. 53% of tracked open issues have had no activity in three months. Only 4% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5,024
New in 7 days: 53
Closed in 7 days: 21
Avg open age: 878 days
Stale 30+ days: 4,703
Stale 90+ days: 4,326

Recent activity

Opened in 7 days: 46
Closed in 7 days: 20
Comments in 7 days: 111
Events in 7 days: 435

Top labels

  • type/bug (11,790)
  • type/enhancement (5,719)
  • severity/major (4,306)
  • severity/moderate (3,579)
  • sig/planner (3,562)
  • sig/sql-infra (2,780)
  • sig/execution (2,296)
  • component/test (1,735)

Detailed Description

TiDB is an open-source, cloud-native distributed SQL database written in Go that provides ACID guarantees with native support for transactions, analytics, and vector search. The project is designed to handle agentic workloads that grow unpredictably while maintaining strong consistency and high performance across horizontally and vertically scalable infrastructure.

The core architecture separates computing from storage, enabling independent scaling of both layers without downtime. TiDB uses a two-phase commit protocol to ensure ACID compliance across distributed transactions spanning multiple nodes, maintaining data correctness even during network partitions or node failures. The system employs a built-in Raft consensus protocol for reliability, with data stored in multiple replicas and transactions committed only after writing to the majority, guaranteeing strong consistency and availability.

TiDB implements hybrid transactional and analytical processing through two storage engines: TiKV, a row-based engine, and TiFlash, a columnar engine. TiFlash uses the Multi-Raft Learner protocol to replicate data from TiKV in real time, ensuring consistent data between both engines. The TiDB Server coordinates query execution across both storage engines to optimize performance for different workload patterns.

MySQL 8.0 compatibility is a central design principle, allowing applications to migrate to TiDB with minimal or no code changes. The project provides data migration tools to facilitate moving application data into TiDB. Cloud-native deployment is supported across public clouds, on-premises environments, and Kubernetes, with TiDB Operator automating cluster operations on Kubernetes and TiDB Cloud offering a fully managed service.

TiDB is released under the Apache 2.0 license with all source code available on GitHub, including enterprise-grade features. The project actively encourages community contributions through good first issues, help wanted labels, and a contribution map detailing contribution opportunities. Community support is provided through Discord, Slack channels in English and Japanese, Stack Overflow, and regional forums including the TiDB Chinese Forum.