News, releases, and deep dives from the team behind Polly, the .NET resilience and transient-fault-handling library.
After months of continuous development, Polly v8 is finally here! In our v8 announcement post, we discussed the background of the Polly project and what motivated us to completely redesign the library with a hyper-focus on performance. We were very...
Continue reading →
UPDATE: May 26, 2023 We have issued a new pull request (Polly V8: Public API Review #1233) to introduce the v8 API to the public. We would love your feedback! Help shape the API ahead of a tentative June release.There...
Continue reading →
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...
Continue reading →
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...
Continue reading →Introducing custom policiesThe Polly team have long wanted to allow users to extend Polly’s capability with custom policies.Polly v7.0 introduces a simple mechanism for authoring custom policies which integrate fully with the existing Polly architecture: the fault-handling syntax, the execution...
Continue reading →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...
Continue reading →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...
Continue reading →In this article we’ll build our first custom Polly policy: a proactive Policy to capture execution timings.Polly polices fall into two categories: reactive (which react to faults) and non-reactive or proactive (which act on all executions). To author a policy...
Continue reading →
Azure Cognitive Services is an excellent series of cloud-based APIs that open up a world of artificial intelligence (AI) opportunities that you can easily add to your applications and data process flow. Each service contains a set of trained and...
Continue reading →
OverviewWhen you define a Polly exception-handling policy, the policy will internally catch matched exceptions and handle them as the policy defines: orchestrate a retry; update circuit-breaker statistics; or channel execution to a fallback.Debugging such executions can however be noisy in...
Continue reading →BackgroundPolly offers both non-generic policies Policy with a generic .Execute<TResult>(...) method, as well as generic policies Policy<TResult>. This article sets out to answer questions Polly users sometimes raise: Why do both exist? And why can’t I just use the generic...
Continue reading →TL;DR In Polly V5.1.0, we’ve extended Context so that it can be used to pass information between different parts of an execution through a policy. Featured Use Cases include honouring RetryAfter headers, and re-establishing authentication automatically.Why Context?Web request frameworks in...
Continue reading →
A few days ago I sat down (virtually) with Bryan Hogan of the NoDogmaPodcast to record a podcast on an Introduction to Polly.In the podcast we talk about common resilience patterns, why you need them, and how you might use...
Continue reading →
This is an exciting day for us, and one we’ve been working toward for several months. Not only have we pushed out a major release (v5.0 alpha), we’re announcing our induction into the .NET Foundation! I’ll get into all of...
Continue reading →
Today we released Polly v5.0 in alpha to Nuget. This is the next step in making Polly a much wider resilience framework for .NET, as Hystrix is for Java.TL;DR, the new resilience policies and features are: Bulkhead isolation - ‘Don’t...
Continue reading →
Over the past ~10 months since the App vNext team has taken over the Polly project from its creator and genius master mind, Michael Wolfenden, Polly has undergone an incredible amount of growth (15 releases in that time!). We’ve since...
Continue reading →