I'd also like someone with experience to contrast redis for these use cases.

Redis is a cache, it's not a queue.

Can you do something similar? I guess, just like you can use a highlighter to paint your house. But the semantics are not correct.

There is Redis Streams, but certainly not without it's problems. Super obscure, not a lot of client support.

Or postgres. If you are under 1000 messages a second it functions well as a transactional queue.

Until table bloat happens.

Yes, Don't why is not mentioned in the article, maybe because is more barebones.