New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rate-limiting by groupKey - new implementation? #1510
Comments
Motivations for this change are here: https://blog.taskforce.sh/bullmq-3-0-release/ |
Thanks for the link. So you're saying this feature is not available anymore unless I upgrade to the pay-for PRO version? |
It is available on BullMQ version 2.x and on Bull, but removed in version >= 3. The feature in the Pro version is a superset of the group functionality in BullMQ that is much more robust and efficient as well. |
Are you going to remove more features from BullMQ in the future? |
Obviously, it is not some kind of long-term plan to remove features, on the contrary more will be added. I hope I made a good explanation in the blog post of why this particular feature was removed, for most users this was an improvement, as the rate limiter works much better now. |
I figured that for my usecase it made more sense to just create a separate queue per logical group and have a fine-tuned global rate limit for each group. As for the docs, I am now only sticking to the code or the automatically generated API docs. But I really appreciate the Patterns and Guide section. They helped me a lot in my architectural decision making. |
I was about to file a bug for the missing
groupKey
property in the InterfaceRateLimiterOptions
when I discovered this commit:81f780a
Where can I find information on the new implementation and how to use it?
Your docs are way out of date. :/
Thanks.
My original error message:
The text was updated successfully, but these errors were encountered: