A
dragonfly
81.5
31,878 stars · license n/a
Databases
tidb leads by 11.4 · clear
A
81.5
31,878 stars · license n/a
B · leads
92.9
40,739 stars · Apache-2.0
dragonfly versus tidb is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dragonfly is written mainly in C++; tidb is written mainly in Go. The composite score is 81.5 for dragonfly and 92.9 for tidb.
tidb has 40,739 GitHub stars to dragonfly's 31,878, a gap of 8,861 (1.28×). Forks are 1,294 for dragonfly and 6,297 for tidb. On the log scale used inside this pair, adoption is 98 versus 100, and the fork community is 82 versus 100.
Push history: dragonfly was last pushed on 17 November 2026 (0 days ago), and tidb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 209 for dragonfly (0.007 per star) and 7,730 for tidb (0.190 per star). Issue-health scores are 84 and 34; activity scores are 100 and 100.
dragonfly is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. tidb is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. License scores in this pair are 30 for dragonfly and 96 for tidb. This is a procurement signal, not legal advice.
Only tidb is marked self-hostable here (40,739 stars, deploy score 100). dragonfly is not (31,878 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: dragonfly is unpriced in this catalog, tidb is open source.
The lead is split. dragonfly is furthest ahead on issue health (84 to 34), while tidb is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
tidb finishes ahead at 92.9 against dragonfly at 81.5, a 11.4 point clear margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | dragonfly | tidb |
|---|---|---|
| GitHub stars | 31,878 | 40,739 |
| Forks | 1,294 | 6,297 |
| Open issues | 209 | 7,730 |
| Adoption | 98 | 100 |
| Activity | 100 | 100 |
| Community | 82 | 100 |
| Issue health | 84 | 34 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 81.5 | 92.9 |
A modern replacement for Redis and Memcached
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.
tidb has more GitHub stars: 40,739 versus 31,878 for dragonfly. The gap is 8,861 stars.
Both were last pushed on 17 November 2026.
Only tidb is marked self-hostable. dragonfly is not.
dragonfly is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. tidb is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
tidb scores 92.9 and dragonfly scores 81.5. This page calls that a clear lead for tidb.