A
dtm
73.5
10,933 stars · BSD-3-Clause
Databases
redis leads by 9.9 · clear
A
73.5
10,933 stars · BSD-3-Clause
B · leads
83.4
77,588 stars · license n/a
dtm versus redis is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. dtm is written mainly in Go; redis is written mainly in C. The composite score is 73.5 for dtm and 83.4 for redis.
redis has 77,588 GitHub stars to dtm's 10,933, a gap of 66,655 (7.10×). Forks are 997 for dtm and 25,072 for redis. On the log scale used inside this pair, adoption is 83 versus 100, and the fork community is 68 versus 100.
Push history: dtm was last pushed on 03 January 2026 (318 days ago), and redis was last pushed on 17 November 2026 (0 days ago). Open issues stand at 88 for dtm (0.008 per star) and 3,122 for redis (0.040 per star). Issue-health scores are 84 and 70; activity scores are 36 and 100.
dtm is listed as BSD-3-Clause, 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. redis 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. License scores in this pair are 96 for dtm and 30 for redis. This is a procurement signal, not legal advice.
Only dtm is marked self-hostable here (10,933 stars, deploy score 100). redis is not (77,588 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: dtm is open source, redis is unpriced in this catalog.
The lead is split. dtm is furthest ahead on license flexibility (96 to 30), while redis is furthest ahead on recent activity (100 to 36). Choose the dimension a rollout cannot compromise on.
redis finishes ahead at 83.4 against dtm at 73.5, a 9.9 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 | dtm | redis |
|---|---|---|
| GitHub stars | 10,933 | 77,588 |
| Forks | 997 | 25,072 |
| Open issues | 88 | 3,122 |
| Adoption | 83 | 100 |
| Activity | 36 | 100 |
| Community | 68 | 100 |
| Issue health | 84 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 73.5 | 83.4 |
A distributed transaction framework, supports workflow, saga, tcc, xa, 2-phase message, outbox patterns, supports many languages.
For developers, who are building real-time data-driven applications, Redis is the preferred, fastest, and most feature-rich cache, data structure server, and document and vector query engine.
redis has more GitHub stars: 77,588 versus 10,933 for dtm. The gap is 66,655 stars.
redis was pushed more recently: 17 November 2026 versus 03 January 2026 for dtm. That is 318 days apart.
Only dtm is marked self-hostable. redis is not.
dtm is listed as BSD-3-Clause, 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. redis 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
redis scores 83.4 and dtm scores 73.5. This page calls that a clear lead for redis.