Considering an Extension Upgrade to Bull MQ

Coffee Lounge
#1

Should I rewrite the a bull extension once again to utilize Bull MQ? That would be V3. This is exciting:

https://docs.bullmq.io/guide/redis-tm-compatibility/dragonfly

https://docs.bullmq.io/

Poll: Your Input Needed! I’d love to gather your thoughts on this potential upgrade. Your feedback is invaluable and will play a crucial role in the decision-making process. Please select one or more options below to share your opinion:

  • No
  • Yes
  • What the heck is bull mq?
  • What the heck is dragonfly?
  • I’m willing to contribute to the extension development financially

0 voters

1 Like
#2

Yes, we are also considering to offer dragonfly as Redis alternative because Redis is now also stepping out of open source and getting more commercial.

Dragonfly is the perfect drop in replacement that is even in many cases faster than Redis self.

3 Likes
#3

We have been using the Bull Queue extension created initially by Ken, and then v2 that you had created - and it has been great.
The code we have has evolved over the year, and is now a bit of a mess - but I was planning to clean it up a bit for our use cases at least.

I have no idea what the changes are (haven’t read up either), but we would be interested in financially contributing if things make sense.
With the production apps, its always costly to change things like this which require a lot of testing to ensure nothing breaks.

1 Like