Thread by @davidfowl

I'm not sure about using redis as a queue, seems like blocking operations block the connection? Also, when using BROP to monitor multiple queues, you end up shuffling the queue names so the queue at the front of this list doesn't take priority (round robin?)

Or do you spin up multiple connections and balance the queues across them? It's a multiplexing problem (reminds me of HTTP/2).

I'm using System.Threading.Channels and Redis to expose a really nuget IAsyncEnumerable<T> implementation. Then using static interfaces to provide the RedisValue -> T.

Here's how that interface is used. You can implement it on your message types and use this method.

Then there's the complicated logic to create redis connections and run BROP commands against it and populate the appropriate channel.