Re:Tokio 1.0 – async runtime for Rust
by kiadimoondi on Wednesday December 23, 2020 @02:51PM
(#25521408)
Can't speak for the commenter, but I used to work for a team couple years ago that used rust and tokio extensively, and some projects were just not a good fit. At the time, futures were well fleshed out but the community hadn't caught up, so we were lacking a futures-compatible postgres and redis client. We wrote the redis client ourselves, and for the main project using rust that was sufficient. But for postgres, that was a show stopper for any other projects we were working on. So we ended up deciding between typescript and go for those.
[ Parent
| on HN ]
Re:Tokio 1.0 – async runtime for Rust
by johnsoft on Wednesday December 23, 2020 @03:52PM
(#25522091)
Just curious, did you consider wrapping the existing sync clients with something like spawn_blocking[1]? If so, what tradeoffs did you find?
[1]: https://docs.rs/tokio/1.0.0/tokio/task/fn.spawn_blocking.htm...
Re:Tokio 1.0 – async runtime for Rust
by ibraheemdev on Wednesday December 23, 2020 @03:19PM
(#25521713)
The ecosystem has moved forward a lot since then. Pretty much all IO libraries provide an asynchronous API now.