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
Hello, thanks for this great library. I used it recently with great success on a project recently.
Now, I've got a system running on several nodes that I'd like to all use the same fuse and rate limit. It looks like these entities live in ETS. Do you think it would be reasonable to extend this to customize configuration storage to allow storing them in a distributed (or external) cache?
The text was updated successfully, but these errors were encountered:
Hello @adherr , I'm very sorry that I didn't see this before. My GitHub notifications must not be properly configured and I never received an email for this, but I will look into that.
As to the issue you've raised, I agree that it would be nice for all the fuse and rate-limit configuration to work seamlessly in clustered applications. The current implementation uses external libraries for the circuit-breaker and rate-limiting behavior, so I'm not sure how much flexibility there is for making those libraries work in clustered mode but I will investigate. I've also been considering dropping the third-party dependencies and making this library more standalone so that it wouldn't be so constrained by such things, so this might prove to be the impetus for doing that.
Thanks for reporting this and I'll update here when I've got a better idea about how to proceed.
Hello, thanks for this great library. I used it recently with great success on a project recently.
Now, I've got a system running on several nodes that I'd like to all use the same fuse and rate limit. It looks like these entities live in ETS. Do you think it would be reasonable to extend this to customize configuration storage to allow storing them in a distributed (or external) cache?
The text was updated successfully, but these errors were encountered: