-
Notifications
You must be signed in to change notification settings - Fork 719
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
Implement Circuit Breaker Pattern #448
Comments
@rizalgowandy Thanks for reaching out and recommending a new feature for Resty. |
Is there any progress on this? It would be quite good to have a built-in cb. |
Bump on this - built in circuit breaker would be very helpful |
Hi @jeevatkm, I was thinking about having the breaker at the client level, and count errors around the client.execute() calls. Still debating if the CB should only count http.Do errors (i.e counting remote server issues only) or all errors (which include resty internal or middleware errors). All input is appreciated 🙂 |
@segevda Thanks for reaching out. I'm currently working on the SSE feature. If you want to take a shot, please use branch We should consider only |
Reviewed-by: ccoVeille <[email protected]>
Co-authored-by: ccoVeille <[email protected]>
Co-authored-by: ccoVeille <[email protected]>
PR merged. |
It will be awesome if resty has a built-in circuit breaker that can be enabled.
This feature protects from too many open files and much more accidents.
Reference: https://github.com/eapache/go-resiliency
The text was updated successfully, but these errors were encountered: