A · level
rocksdb
90.9
32,285 stars · GPL-2.0
Databases
Too close to call · 90.9 to 91.3
A · level
90.9
32,285 stars · GPL-2.0
B · level
91.3
25,194 stars · AGPL-3.0
rocksdb versus TDengine is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. rocksdb is written mainly in C++; TDengine is written mainly in C. The composite score is 90.9 for rocksdb and 91.3 for TDengine.
rocksdb has 32,285 GitHub stars to TDengine's 25,194, a gap of 7,091 (1.28×). Forks are 7,033 for rocksdb and 5,011 for TDengine. On the log scale used inside this pair, adoption is 100 versus 98, and the fork community is 100 versus 96.
Push history: rocksdb 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 1,855 for rocksdb (0.057 per star) and 454 for TDengine (0.018 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.
rocksdb is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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 64 for rocksdb and 52 for TDengine. This is a procurement signal, not legal advice.
In Databases, both rocksdb (32,285 stars) and TDengine (25,194 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: rocksdb is open source, TDengine is open source.
The lead is split. rocksdb is furthest ahead on license flexibility (64 to 52), while TDengine is furthest ahead on issue health (84 to 52). Choose the dimension a rollout cannot compromise on.
Composite score: rocksdb 90.9, TDengine 91.3. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | rocksdb | TDengine |
|---|---|---|
| GitHub stars | 32,285 | 25,194 |
| Forks | 7,033 | 5,011 |
| Open issues | 1,855 | 454 |
| Adoption | 100 | 98 |
| Activity | 100 | 100 |
| Community | 100 | 96 |
| Issue health | 52 | 84 |
| License | 64 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 90.9 | 91.3 |
A library that provides an embeddable, persistent key-value store for fast storage.
High-performance, scalable time-series database designed for Industrial IoT (IIoT) scenarios
rocksdb has more GitHub stars: 32,285 versus 25,194 for TDengine. The gap is 7,091 stars.
rocksdb was pushed more recently: 17 November 2026 versus 15 November 2026 for TDengine. That is 2 days apart.
Yes. This catalog marks both rocksdb and TDengine as self-hostable. Confirm each project's deploy docs before you plan a migration.
rocksdb is listed as GPL-2.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. 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.
Neither tool clears a one-point margin. rocksdb scores 90.9 and TDengine scores 91.3.