Polly VS Hangfire

Polly - repositorio oficial

The swap API may return UPSTREAM_ERROR (502) during transient routing failures or RATE_LIMITED (429) when exceeding approximately 30 requests per minute. Use Polly or the built-in Microsoft.Extensions.Http.Resilience package in .NET 8 for production-grade retry policies.

📖 Official Polly Documentation 🔗 Microsoft's guide on HTTP resilience with Polly

If you're using Polly for resilience, there's a separate integration package:

The file downloading logic is wrapped in a Polly AsyncRetryPolicy and is essentially 3 lines (20–22).

Polly

This is probably one of the most useful "cloud" patterns out there and it is fairly easy to implement. There are great articles and implementations, like Polly, already on the internet about this pattern so why another one?

Polly Documentation: Polly Official Site Circuit Breaker Design Pattern: Microsoft Learn Microservices Best Practices: Microservices on .NET

Custom HTTP handlers are well known as a mechanism to manage cross-cutting concerns around HTTP requests. The calling application has control over the HTTP handler pipeline, so it can be reconfigured, reordered, or even rebuilt from scratch. Decorating a client with a Token Management Handler or a custom Polly policy is easy... assuming the client accepts an HttpClient parameter in its constructor, and you haven't messed with the natural order of things by obstructing the client customization in some way (I really don't want to show how).

In our applications, we should wrap all requests to remote services in code that implements a retry policy that follows one of the strategies I listed earlier. If you are a .NET developer like myself, you may be familiar with the Polly library. Golang has a library called Retry, and there are numerous third-party libraries for Python and Java.

Hangfire (.NET) - Background job processing

Hangfire is one of the most powerful background job processing libraries in the .NET ecosystem. Whether you're working with ASP.NET Core, .NET Framework, or integrating with Azure Services, Hangfire simplifies job scheduling, execution, and monitoring.

SignalR and .Net work so well together. We also heavily leverage Hangfire (https://github.com/HangfireIO/Hangfire) in our apps for any async/background processes as well.

Hangfire is a popular library for background job scheduling in .NET that provides support for recurring jobs, real-time monitoring, and persistent storage.

By following this guide, you have integrated Hangfire into your . NET 8 project and scheduled an API call using Hangfire with SQL Server as the storage provider. This setup ensures your API is called regularly according to the specified schedule. For more advanced Hangfire configurations and storage options, refer to the official Hangfire documentation.

6. Hangfire

Unpopular opinion incoming... What I see is yet another way that the backend JS world is finally achieving something .NET had years ago[0].

Node/Deno/Bun/etc. + npm sounds super straightforward at first glance (and it is at first). But I've thought for years that it's far easier to be productive as an organization on .NET in Visual Studio, since it's simpler to design, deliver, and maintain infrastructure.

[0] https://www.hangfire.io/

you can read about it here HangFire Documentation