https://github.com/minhhungit/ConsoleTableExt
Polly
Our great sponsors
| https://github.com/minhhungit/ConsoleTableExt | Polly | |
|---|---|---|
| - | 52 | |
| 318 | 12,991 | |
| - | 1.4% | |
| 3.9 | 9.8 | |
| 6 months ago | 2 days ago | |
| C# | C# | |
| MIT License | BSD 3-clause "New" or "Revised" License |
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.
https://github.com/minhhungit/ConsoleTableExt
We haven't tracked posts mentioning https://github.com/minhhungit/ConsoleTableExt yet.
Tracking mentions began in Dec 2020.
Polly
-
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
-
Getting back into C# after a hiatus, any good reading material recommendations to get back up to speed? Been using Kotlin recently, and got quite a lot of experience in engineering.
Runs in containers nicely, has good integration with Kafka, RabbitMQ, gRPC, etc. for Microservices communication. Implements resiliency patterns you'd want in Microservices via Polly. Has a decent Dependency Injection framework built in by default.
-
What your hidden nuget gems ?
It's in no way hidden. But I use Polly all the time.
-
Message Queueing
Depending if the sender or the reciever is down, you can also try Polly http://www.thepollyproject.org/
- How To Implement Retries Without Cluttering Your Code
What are some alternatives?
HidLibrary - This library enables you to enumerate and communicate with Hid compatible USB devices in .NET.
MediatR - Simple, unambitious mediator implementation in .NET
CsvHelper - Library to help reading and writing CSV files
Hangfire - An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required
YoutubeExplode - Abstraction layer over YouTube's internal API
FluentValidation - A popular .NET validation library for building strongly-typed validation rules.
Scientist.net - A .NET library for carefully refactoring critical paths. It's a port of GitHub's Ruby Scientist library
Redis - Redis is an in-memory database that persists on disk. The data model is key-value, but many different kind of values are supported: Strings, Lists, Sets, Sorted Sets, Hashes, Streams, HyperLogLogs, Bitmaps.
ENet-CSharp - Reliable UDP networking library
Refit - The automatic type-safe REST library for .NET Core, Xamarin and .NET. Heavily inspired by Square's Retrofit library, Refit turns your REST API into a live interface.
Hashids.net - A small .NET package to generate YouTube-like hashes from one or many numbers. Use hashids when you do not want to expose your database ids to the user.
Flurl.Http - Fluent URL builder and testable HTTP client for .NET