There is no question that the Polly library has had a big impact on the .NET community in providing useful resilience and transient fault handling policies in an accessible way to millions of projects. Given its widespread use and popularity, we are responsible as maintainers for ensuring the library remains
This is a cross-post from elvanydev.com.
In the latest post, I introduced you Simmy and we saw all the benefits of chaos engineering and how Simmy helps us making chaos in our systems injecting faults, latency or custom behavior in order to make sure that our resilience strategies are
This is a cross-post from elvanydev.com.
What Is Simmy?
Simmy is a chaos-engineering and fault-injection tool based on the idea of the Netflix Simian Army, integrating with the Polly resilience project for .NET, Simmy takes advantage of the power of Polly to help you to answer these questions:
- Is
In the previous articles in this series, we have seen how to author custom reactive and proactive Polly policies:
- Part I: Introducing custom Polly policies and the Polly.Contrib
- Part II: Authoring a proactive custom policy (a policy which acts on all executions)
- Part III: Authoring a reactive custom policy
In this article we'll build our first reactive custom Polly policy: a policy to log exceptions or fault-results.
Polly polices fall into two categories: reactive (which react to configured faults) and non-reactive / proactive (which act on all executions). To author a proactive policy, see Part II: Authoring a proactive custom