You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First and foremost, thanks for developing this awesome tool.
Is your feature request related to a problem? Please describe.
I tested the System in the multi-clustering environment and I realized if an Event is triggered, all consumers run the process or if a delayed job is triggered all handlers will be triggered and the process will be duplicated all around the clusters.
Describe the solution you'd like
A DLM(Distributed lock manager) should be implemented for managing the connected Apps with their clusters.
Describe alternatives you've considered
Using BullMQ
The text was updated successfully, but these errors were encountered:
Ya, right now this runs on inngest.com and is ephemeral when running inngest dev. Soon (as in, early next year) we'll likely support self hosting by nature of the backend having less iterations. We're releasing things like debounce, live tails, etc. which are going to require deep knowledge of our systems to migrate — and until it's stable we know it'll be a pain for you to keep up with the changes.
First and foremost, thanks for developing this awesome tool.
Is your feature request related to a problem? Please describe.
I tested the System in the multi-clustering environment and I realized if an Event is triggered, all consumers run the process or if a delayed job is triggered all handlers will be triggered and the process will be duplicated all around the clusters.
Describe the solution you'd like
A DLM(Distributed lock manager) should be implemented for managing the connected Apps with their clusters.
Describe alternatives you've considered
Using BullMQ
The text was updated successfully, but these errors were encountered: