Rust gives you freedom in designing a perfect long-running service, but if you are not doing it from scratch you will be relying on an async runtime like Tokio.

Rust gives you freedom in designing a perfect long-running service, but if you are not doing it from scratch you will be relying on an async runtime like Tokio. Go's flawed memory model nonwithstanding this use case is simple enough to be able to avoid or recover from races and leaks with less work. When concurrency is important and you are not designing lock-free algorithms I would sooner go with Erlang or Elixir than Rust. If you are designing concurrent algorithms with liveness guarantees you are in the TLA+, fighting the C11 memory model, unsafe Rust territory.