You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm a big fan of doing it that way, it gives the consumer a bit more control over how they use it, I use polly all the time for retry polices. The main reason I use it though was mentioned in this issue #20. It does mean exposing some of the internals of the broker which I don't think @hassanhabib likes to much. I may be wrong though :)
Hi @jodendaal, I think I will create a new PR to incorporate different resiliency related issues with Polly.
I already created a PR #84 where I registered HttpClient using Microsoft.Extensions.Http and used Delegating Handler in order to delegate the responsibility of adding Bearer Token and OrganizationId to the request headers. Injected IHttpClientFactory into broker to resolve HttpClient.
After this PR gets merged, I'll use Polly to implement resiliency in HttpClient.
See:
https://learn.microsoft.com/en-us/dotnet/architecture/microservices/implement-resilient-applications/implement-http-call-retries-exponential-backoff-polly
The text was updated successfully, but these errors were encountered: