Evaluating Rust vs Go for a new network proxy handling 50k+ concurrent connections with strict p99 latency targets under 5ms. Go gives us faster iteration but GC pauses are a concern. Rust's async ecosystem is maturing but debugging is painful. What's been your experience in production?
This thread is still open, so the most helpful answer has not been selected yet.
The choice depends on your latency budget and team constraints. Go's goroutine scheduler handles tens of thousands of concurrent connections with minimal memory overhead and fast startup — ideal if you're building a gateway or proxy where development velocity matters. Rust gives you deterministic latency with zero-cost abstractions and no GC pauses, which matters for sub-millisecond tail latencies at scale. That said, Rust's compile times and borrow checker learning curve slow iteration. I'd lean Go unless p99 latency under load is a hard requirement, then invest in Rust with Tokio for async networking.