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
Which policies share the state across requests? #494
Comments
Yes.
A
CircuitBreaker and Bulkhead. CircuitBreaker's purpose to count and act according to success/fail metrics across calls placed through the policy. It stores those counts in internal state. The intended functional consequence is that if you share a
Bulkhead's purpose is to limit concurrency of calls placed through it. Each single
All policies can be stored centrally (eg in a |
Thank you so much for your accurate answer @reisenberger! |
Published a wiki article to cover the topic. |
@reisenberger Thanks for always improve the documentation! |
Hi,
I would like to know which policies share the state across requests. What I understand is circuit-breaker instances can be shared across multiple call sites, it means if I store the instance, let's say, into a
PolicyRegistry
, cache, or another storage which hold the object between requests, it keeps the state of the circuit?For example, my circuit breaker is configured to break the circuit after 3 exceptions, so, I would like that the next incoming requests to that resource fail fast instead to try to execute it. is it possible? also, it applies for Retry as well?
The text was updated successfully, but these errors were encountered: