Our great sponsors
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
Why use this or Flume over the crossbeam multi-producer multi-consumer channel [1]? I thought crossbeam was well-regarded and pretty much the unofficial standard library for sync code.
https://github.com/crossbeam-rs/crossbeam/tree/master/crossb...
The repository seems abandoned; or maybe complete?
At work we use flume, which is another capable multi-producer, multi-consumer async-capable channel [1]. It's great for shuffling data between threads, as well as between async tasks, and between threads and async tasks. Basically any time you want to pieces of code to exchange data or signals without pesky shared state.
1: https://github.com/zesterer/flume
Related posts
- Where can I read about how to write a safe API for unsafe code?
- I wrote a post about background processing library - Fang
- Loole, A safe sync/async multi-producer, multi-consumer channel, Boosted Async Performance Up to 17%
- multi-producer multi-consumer channels for message passing python library
- I needed to write a simple multi-threaded message processing queue in C++ today. Makes me really appreciate how easy this is to do in Rust.