Decision Workspace
helixrouter vs tokio-sticky-channel vs amqprs
Side-by-side comparison of Rust crates
51
helixrouter
experimentalv1.0.2
Adaptive async compute routing engine: per-job strategy selection (inline/spawn/pool/batch/drop) driven by live pressure, EMA latency, and online-learned quality estimates.
51
tokio-sticky-channel
experimentalv0.1.3
Sticky channel pattern for Tokio - routes messages to specific receivers based on ID hash for consistent message delivery
70
amqprs
stablev2.1.5
AMQP 0-9-1 client implementation for RabbitMQ
Core Metrics
| helixrouter | tokio-sticky-channel | amqprs | |
|---|---|---|---|
| Health Score | 51 | 51 | 70 |
| Total Downloads | 36 | 1.5K | 639.6K |
| 30d Downloads | 36 | 7 | 44.3K |
| Dependents | 0 | 0 | 230 |
| Releases | 3 | 4 | 77 |
| Last Updated | 8d ago | 253d ago | 8d ago |
| Age | 9d | 8m | 3y 3m |
Health Breakdown
helixrouter
Maintenance
13
Quality
15
Community
6
Popularity
2
Documentation
15
tokio-sticky-channel
Maintenance
15
Quality
13
Community
6
Popularity
4
Documentation
13
amqprs
Maintenance
18
Quality
18
Community
12
Popularity
7
Documentation
15
Technical Details
| helixrouter | tokio-sticky-channel | amqprs | |
|---|---|---|---|
| Version | 1.0.2 | 0.1.3 | 2.1.5 |
| Stable (≥1.0) | ✓ Yes | ✗ No | ✓ Yes |
| License | MIT | MIT/Apache-2.0 | MIT |
| Dependencies | 15 | 4 | 15 |
| Crate Size | 142KB | 20KB | 79KB |
| Features | 2 | 0 | 5 |
| Yanked % | 0.0% | 0.0% | 9.1% |
| Edition | 2021 | 2024 | 2021 |
| MSRV | 1.81 | — | 1.71 |
| Owners | 1 | 1 | 1 |
Links
Quick Verdict
- •amqprs leads with a health score of 70/100, but none of the options score above 80.
- •amqprs is depended on by 230 crates — strongest ecosystem trust.
- •tokio-sticky-channel is pre-1.0 — API may change.