A
dragonfly
82.6
31,878 stars · license n/a
Databases
TDengine leads by 9.3 · clear
A
82.6
31,878 stars · license n/a
B · leads
91.9
25,194 stars · AGPL-3.0
dragonfly versus TDengine 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++; TDengine is written mainly in C. The composite score is 82.6 for dragonfly and 91.9 for TDengine.
dragonfly has 31,878 GitHub stars to TDengine's 25,194, a gap of 6,684 (1.27×). Forks are 1,294 for dragonfly and 5,011 for TDengine. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 84 versus 100.
Push history: dragonfly was last pushed on 17 November 2026 (0 days ago), and TDengine was last pushed on 15 November 2026 (2 days ago). Open issues stand at 209 for dragonfly (0.007 per star) and 454 for TDengine (0.018 per star). Issue-health scores are 84 and 84; 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. TDengine is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 30 for dragonfly and 52 for TDengine. This is a procurement signal, not legal advice.
Only TDengine is marked self-hostable here (25,194 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, TDengine is open source.
The lead is split. dragonfly is furthest ahead on adoption (100 to 98), while TDengine is furthest ahead on self-hosting (100 to 35). Choose the dimension a rollout cannot compromise on.
TDengine finishes ahead at 91.9 against dragonfly at 82.6, a 9.3 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 | TDengine |
|---|---|---|
| GitHub stars | 31,878 | 25,194 |
| Forks | 1,294 | 5,011 |
| Open issues | 209 | 454 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 84 | 100 |
| Issue health | 84 | 84 |
| License | 30 | 52 |
| Self-hosting | 35 | 100 |
| Composite | 82.6 | 91.9 |
A modern replacement for Redis and Memcached
High-performance, scalable time-series database designed for Industrial IoT (IIoT) scenarios
dragonfly has more GitHub stars: 31,878 versus 25,194 for TDengine. The gap is 6,684 stars.
dragonfly was pushed more recently: 17 November 2026 versus 15 November 2026 for TDengine. That is 2 days apart.
Only TDengine 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. TDengine is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
TDengine scores 91.9 and dragonfly scores 82.6. This page calls that a clear lead for TDengine.