polly

I'm writing a service which will be connecting to a remote postgres server. I'm looking for a good way to determine which exceptions should be treated as transient (worth retrying), and how to define an appropriate policy for connecting to a remote database. The service is using Npgsql for the data access. The documentation says that Npgsql will throw a PostgresException for sql errors and an NpgsqlException for "server related issues". So far the best I have been able to come up with is to assume all exceptions that are not PostgresExceptions should be treated as possibly transient, worth

I have a query, IGetHamburgers , that calls an external API. I've registered the implementation of IGetHamburgers in my DI container as a Singleton. Im using Polly as a Circuitbreaker, if two requests fails the circuit will open. My goal is that all calls to the Hamburger api should go through the same circuitbreaker, if GetHamburgers fails, then all other calls should fail as well. How should I use my Policy? Should I register my Policy as a field like this: private Policy _policy; private Policy Policy { get { if(this_policy != null) { return this_policy; } this._policy = Policy .Handle

I consider to use Polly to create policy to log exception and rethrow. I didn't find an existing method that allow it out of the box , but some options that I see are Fallback // Specify a substitute value or func, calling an action (eg for logging) if the fallback is invoked. Policy.Handle<Whatever>() .Fallback<UserAvatar>(UserAvatar.Blank, onFallback: (exception, context) => { _logger.Log(exception, context); throw exception; }); Question: is it ok to throw exception from Fallback? Timeout Policy.Timeout(1, T30meoutStrategy.Pessimistic, (context, timespan, task) => { task.ContinueWith(t => {

This is a FULLY working example (Copy/paste it and play around, just get the Polly Nuget) I have the following Console app code which makes a POST request to an HTTP client sandbox on ' http://ptsv2.com/t/v98pb-1521637251/post ' (you can visit this link " http://ptsv2.com/t/v98pb-1521637251 " to see the configuration or make yourself a "toilet"): class Program { private static readonly HttpClient _httpClient = new HttpClient() ; //WHY? BECAUSE - https://aspnetmonsters.com/2016/08/2016-08-27-httpclientwrong/ static void Main(string[] args) { _httpClient.BaseAddress = new Uri(@"http://ptsv2.com

With Polly I'd like to have my policy definition and the execution of that policy in two different statements, as in: // Policy definition var policy = Policy .HandleResult<IRestResponse>(predicate) .Retry(2); // Policy execution policy.ExecuteAndCapture(() => { DoSomethingAndReturnAnIRestResponse(); }; I want to do it this way so I can get better reuse of my retry policies, e.g. for use in dependency injection. I'm trying to understand if there's any considerations when splitting up the policy and the execution in this way, for example if there's any "state" (for lack of a better term) that