Introduce NonReactiveResilienceStrategy
#1476
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Details on the issue fix or feature implementation
The follow-up of #1462 that introduces the base class for non-reactive resilience strategies.
Additional changes:
ResilienceStrategy
internal (similar toResilienceStrategy<T>
). We now have full control over these top-level types.This change make the decision when implementing a new resilience strategy straightforward:
NonReactiveResilienceStrategy
when you want to implement non-reactive strategy.ReactiveResilienceStrategy<T>
when you want to implement reactive strategy.Confirm the following