Polly
Polly is a .NET resilience and transient-fault-handling library that allows developers to express policies such as Retry, Circuit Breaker, Timeout, Bulkhead Isolation, and Fallback in a fluent and thread-safe manner. From version 6.0.1, Polly targets .NET Standard 1.1 and 2.0+. (by App-vNext)
Jering.Javascript.NodeJS
Invoke Javascript in NodeJS, from C# (by JeringTech)
| Polly | Jering.Javascript.NodeJS | |
|---|---|---|
| 56 | 1 | |
| 13,836 | 477 | |
| 0.3% | 0.0% | |
| 9.6 | 6.8 | |
| 10 days ago | over 1 year ago | |
| C# | C# | |
| BSD 3-clause "New" or "Revised" License | GNU General Public License v3.0 or later |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Polly
Posts with mentions or reviews of Polly.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2025-03-28.
-
How To Implement Retries and Resilience Patterns With Polly and Microsoft Resilience
Polly
-
Tripping the circuit
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?
-
Implement Circuit Breaker using Polly in .Net Core 8
Polly Documentation: Polly Official Site Circuit Breaker Design Pattern: Microsoft Learn Microservices Best Practices: Microservices on .NET
-
Designing HTTP API clients in .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).
-
The Retry Pattern and Retry Storm Anti-pattern
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.
-
Http calls on mobile, what is the preferred way / best practice
Another question that rises is, would it be better to use some HttpClient package to handle the requests, like Refit in combination with Polly. But then again, it seems Refit also uses the HttpClient factory, which was a bad thing according to the previous?
-
[Question] HttpClient does not recover from error
D'Oh! Sorry, not PolySharp. I meant Polly. Too many similarly-named libraries!
-
I thought "Availability Groups" would be 100% "seamless"
Everywhere I've worked with AGs, we've worked with the application team to add retry logic to help make things a bit more seamless to end users. There are libraries out there that can make this pretty easy - Polly is one that I've used a few times, but there are others.
-
Do you really need "microservices"?
Fallacy 1: The network is reliable. If system 2 works perfectly well, but is not accessible for service 1 due to network issues, service 2 is still unavailable. This is why timeouts, service breakers and retry policies exist. A great tool for .NET to handle common network issues is Polly, but even when using a tool like this, the network is still not completely reliable.
-
Only "exit 1" if VISIBLE errors are thrown during script invocation, ignoring try/catch blocks
I see. Then I don't have any better idea right now, but I do want to suggest that if your script is mostly API calls and you want to be able to deal with failures then take a look at the polly library: https://github.com/App-vNext/Polly
Jering.Javascript.NodeJS
Posts with mentions or reviews of Jering.Javascript.NodeJS.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-10-21.
-
Whatever happened to Java interop?
I am currently using this library to run node from C# for exporting HighCharts to images using the highcharts-export-server library in node: https://github.com/JeringTech/Javascript.NodeJS works great.
What are some alternatives?
When comparing Polly and Jering.Javascript.NodeJS you can also consider the following projects:
MediatR - Simple, unambitious mediator implementation in .NET
Jint - Javascript Interpreter for .NET
FluentValidation - A popular .NET validation library for building strongly-typed validation rules.
Redis - For developers, who are building real-time data-driven applications, Redis is the preferred, fastest, and most feature-rich cache, data structure server, and document and vector query engine.
Jurassic - A .NET library to parse and execute JavaScript code.