Decision Workspace
netdb vs c-ares-resolver vs tokio-retry
Side-by-side comparison of Rust crates
36
netdb
growingv0.1.0
Access to network-related name databases
67
c-ares-resolver
stablev12.0.0
An asynchronous DNS resolver, backed by c-ares.
66
tokio-retry
growingv0.3.2
Extensible, asynchronous retry behaviours for futures/tokio
Core Metrics
| netdb | c-ares-resolver | tokio-retry | |
|---|---|---|---|
| Health Score | 36 | 67 | 66 |
| Total Downloads | 2.6K | 226.3K | 92.4M |
| 30d Downloads | 0 | 1.7K | 1.5M |
| Dependents | 6 | 28 | 2.0K |
| Releases | 1 | 48 | 11 |
| Last Updated | 3360d ago | 7d ago | 34d ago |
| Age | 9y 2m | 9y 9m | 9y 4m |
Health Breakdown
netdb
Maintenance
1
Quality
15
Community
5
Popularity
4
Documentation
11
c-ares-resolver
Maintenance
18
Quality
20
Community
10
Popularity
6
Documentation
13
tokio-retry
Maintenance
14
Quality
16
Community
14
Popularity
8
Documentation
14
Technical Details
| netdb | c-ares-resolver | tokio-retry | |
|---|---|---|---|
| Version | 0.1.0 | 12.0.0 | 0.3.2 |
| Stable (≥1.0) | ✗ No | ✓ Yes | ✗ No |
| License | MIT | MIT | MIT |
| Dependencies | 3 | 6 | 4 |
| Crate Size | 7KB | 26KB | 10KB |
| Features | 0 | 4 | 2 |
| Yanked % | 0.0% | 2.1% | 0.0% |
| Edition | — | 2024 | 2018 |
| MSRV | — | — | 1.85 |
| Owners | 1 | 1 | 2 |
Links
Quick Verdict
- •c-ares-resolver leads with a health score of 67/100, but none of the options score above 80.
- •tokio-retry has the most downloads (92.4M), suggesting wider adoption.
- •tokio-retry is depended on by 2.0K crates — strongest ecosystem trust.
- •⚠ netdb has not been updated in over a year.
- •netdb, tokio-retry are pre-1.0 — API may change.