CsvHelper VS Polly

I would also say either a logging framework or one of the many NuGet packages. Like CsvHelper.

I've been using CsvHelper for a long time and I quite like it. It's flexible and configurable enough to suit all my needs. Though the authors have unpleasant habit of introducing breaking changes (currently they are at major version 30).

It's really slow compared to (for example) csvhelper. I tried to use the built in microsoft stuff to handle a data transformation routine using excel files, turning them into csvs and using the csv library sped up the process from 3-4 minutes to about 8 seconds.

How might it compare to https://www.nuget.org/packages/CsvHelper/?

Let me guess, you replaced a string.Split(',') with CsvHelper?

I use CSVHelper https://joshclose.github.io/CsvHelper/ it has a WriteRecords function that will write out your objects

I would recommend looking at this popular library for reading / writing to csv files. https://joshclose.github.io/CsvHelper/

This is probably a bit churlish to complain about, since it's an entirely free tool that has saved me a lot of time and effort, but I'm baffled by the documentation for CsvHelper by Josh Close.

https://joshclose.github.io/CsvHelper/ is a good library for creating CSVs, but you need to tell us more about who is consumer of this export and may be there is a more direct approach

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.

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?

D'Oh! Sorry, not PolySharp. I meant Polly. Too many similarly-named libraries!

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.

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.

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

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.

It's in no way hidden. But I use Polly all the time.

Depending if the sender or the reciever is down, you can also try Polly http://www.thepollyproject.org/