Thanks, definitely makes sense to use Disque for messaging and Redis for caching/storage, and for messaging too when you need ephemeral messaging without guarantees, but you need to control very well the semantics, so in Redis you can build your messaging thing using its primitives. But for reliable message exchanges, with guaranteed at least once delivery, Disque is the thing to use (or other good & reliable message queues).
I wonder if it makes sense to use Disque in the same environment as Redis, since we have use cases for both a key-value store as well as a job queue.