Status of the project

[oliverjanik]

Is this project done? Can it be declared 1.0 Stable?

What are the plans for the future?

[mtdavidson]

Just came here wondering the same thing. There haven't been any updates since April and still quite a few outstanding pull requests. Be really great to know where the project stands so can either embrace it or look for an alternative if its been abandoned. In particular I'd love to see the DELAY for NACK support added #188 as this would make the concept of retries significantly better.

[antirez]

Hello, I hope to continue the development after the end of October, when Redis 4.0 will be released. Sorry for the delay, I was not able to have the free time I expected to have recently... I think that the first thing I'll do is to release 1.0 stable, but immediately after there is to catch up with the changes made in Redis that are applicable to Disque as well. Cheers.

[antirez]

P.S. It's worth to note that in the meantime, Redis got a modules API... and I want to extend the module API in order to support a Cluster API to exchange messages among nodes. It would be cool to rewrite Disque as a module for Redis. Disque would be distributed still as a standalone project probably, and would be identical, but the great stuff would be that we could reuse the whole Redis core effortless and the upgrade of the Redis internals would be trivial. Not sure if this is the way to go but to consider for sure...

[mtdavidson]

Great to know @antirez I'm sure I speak for everyone when I say thanks for all the hard work and look forward to 1.0 :)

[erikdubbelboer]

@antirez is there a place to track the implementation of cluster support for modules? I would also be interested in this for https://github.com/erikdubbelboer/discnt

[skyrocknroll]

@antirez Awesome 👍 Thanks for your update. We are internally using disque in production. Everytime when i pitch for disque for more modules i need to go though the line "No stable version is released yet". Now we are sure 1.0 going to be released. 💯

[kamilion]

Looking forward to a 1.0 release -- will make it tons easier to package in my PPA. Came from python-rq, disque provides cleaner feeling componentry for a task queue.

[derekperkins]

Very interested in disque as a Redis 4.0 module. Spread out in a kubernetes cluster, Redis could act as my queue and my cache, leaving me with only one system to manage.

[debrouxl]

I'm interested in disque as well, especially when reimplemented as a Redis module, on top of built-in messaging in a Redis cluster :)

[galdiolo]

From the Redis 4.2 roadmap: "reimplementation of Disque as a Redis module".
Great!

[galdiolo]

Just now in Twitter from the author: "So happy that people still mention Disque was good. I’m actively porting it as a Redis module. Hence all the changes you saw in the Redis Modules APIs recently."
https://twitter.com/antirez/status/984449710231564289

[galdiolo]

Today in Twitter from the author: "Redis modules have two new set of APIs: timers and cluster. The Cluster API is not about "Redis Cluster", is a cluster message bus abstraction so that you can write distributed systems with Redis. I'm re-writing Disque on top of those new APIs, as a Redis module."
https://twitter.com/antirez/status/1001480576803704835