A
QuestDB
89.9
17,538 stars · Apache-2.0
Databases
tidb leads by 3.0 · narrow
A
89.9
17,538 stars · Apache-2.0
B · leads
92.9
40,739 stars · Apache-2.0
QuestDB versus tidb is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. QuestDB is written mainly in Java; tidb is written mainly in Go. The composite score is 89.9 for QuestDB and 92.9 for tidb.
tidb has 40,739 GitHub stars to QuestDB's 17,538, a gap of 23,201 (2.32×). Forks are 1,701 for QuestDB and 6,297 for tidb. On the log scale used inside this pair, adoption is 92 versus 100, and the fork community is 85 versus 100.
Push history: QuestDB 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 1,515 for QuestDB (0.086 per star) and 7,730 for tidb (0.190 per star). Issue-health scores are 52 and 34; activity scores are 100 and 100.
Both QuestDB and tidb are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Databases, both QuestDB (17,538 stars) and tidb (40,739 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: QuestDB is open source, tidb is open source.
The lead is split. QuestDB is furthest ahead on issue health (52 to 34), while tidb is furthest ahead on fork community (100 to 85). Choose the dimension a rollout cannot compromise on.
tidb finishes ahead at 92.9 against QuestDB at 89.9, a 3.0 point narrow 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 | QuestDB | tidb |
|---|---|---|
| GitHub stars | 17,538 | 40,739 |
| Forks | 1,701 | 6,297 |
| Open issues | 1,515 | 7,730 |
| Adoption | 92 | 100 |
| Activity | 100 | 100 |
| Community | 85 | 100 |
| Issue health | 52 | 34 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.9 | 92.9 |
QuestDB is a time-series database with SQL and a focus on ingestion speed. It is used for metrics, market data, and other timestamp-heavy workloads.
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 17,538 for QuestDB. The gap is 23,201 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both QuestDB and tidb as self-hostable. Confirm each project's deploy docs before you plan a migration.
QuestDB 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. 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 QuestDB scores 89.9. This page calls that a narrow lead for tidb.