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.
Context?Web request frameworks in .NET such as ASP.NET
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 them - starting with well-known patterns such as Retry
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:
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 the details, but first, I'd like to step back
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 set up the project Wiki, created a sample project to