Towel VS Polly

Towel - Throw in the towel! data structures, algorithms, mathematics, metadata, extensions, console, and more - https://github.com/ZacharyPatten/Towel

PacMan is... a PacMan clone in the console. Get the dots. Dodge the ghosts. It's not intended to be very faithful though. I didn't research the AI of the ghost, I just came up with my own AIs that worked. Here is what I did for the ghost AIs:     - Ghost a: follows you via Dijkstra Path Finding and updates every 6 frames (faster)     - Ghost b: randomly moves and updates every 6 frames (faster)     - Ghost c: follows you via Dijkstra Path Finding and updates every 12 frames (slower)     - Ghost d: randomly moves and updates every 12 frames (slower) Note: for this game I pulled in a reference to my nuget package Towel because it includes generic versions of the Dijkstra Path Finding algorithm.

Can you give an example? BCL covers the most common algorithms and data structures, so...? There's also a whole pack of additional algorithms and data structures by u/ZacharyPatten: https://github.com/ZacharyPatten/Towel

Unit Tests

Source Code

I have a GitHub project with generic data structures and algorithms here: https://github.com/ZacharyPatten/Towel It has 18 of the common comparison-based sorting algorithms.

I don't know specifically what you are looking for, but I have a project called Towel that has generic vectors. If interested: https://github.com/ZacharyPatten/Towel.

https://github.com/ZacharyPatten/Towel/blob/070d454f3fcdc5c632bf68547911718b324cf6ae/Examples/DataStructures/Program.cs#L247

Notice how algorithm #1Pool Tracking is dependent on the range of possible values while algorithm #2 Roll Tracking is not. This means if you have a relatively large range of values, then algorithm #2 is faster, otherwise algorithm #1 is faster. So if you want the most efficient method, you just need to compare those runtime complexities based on the parameters and select the most appropriate algorithm. Here is what my "Next" overload currently looks like: See Source Code Here

Here is an example if interested: https://github.com/ZacharyPatten/Towel/blob/master/Examples/CommandLine/Program.cs All I have to do is add the [Command] attribute onto the methods and call "HandleArguments".

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/