Replies: 1 comment
-
The main thing I can think of is the challenge of keeping the .lua scripts from the main BullMQ package synced with the go version. Also it would be useful if the version number of the go package mimics the version number of the node package, so that it can be easily identified if the are using the exact same .lua scripts and thus compatible with each other. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
We’ve been working on a Go worker library for BullMQ, inspired by Codycody31’s gobullmq and my own fork KTBsomen/gobullmq. It’s a mostly working, duct-taped solution that supports both Redis standalone and cluster modes.
Our goal is to enable seamless integration between Node.js BullMQ producers and Go-based workers, making it easier to build scalable, polyglot job processing systems.
Now, we’d love to get some feedback from the Node.js community:
Has anyone tried something similar?
Any suggestions for improvements or missing features?
Would you be interested in helping test and stabilize the library?
Are there common pain points we should address?
If you’re curious or want to contribute, please check out the repos and share your thoughts:
https://github.com/Codycody31/gobullmq
https://github.com/KTBsomen/gobullmq
Thanks for your time and help!
Beta Was this translation helpful? Give feedback.
All reactions