Principia VS Polly

Principia is extremely impressive, they document all their math here: https://github.com/mockingbirdnest/Principia/tree/master/doc...

One interesting detail is that the source code makes extensive use of non-ASCII identifiers, for mathematical symbols and for the names of mathematicians. One of the two primary contributors is also an active contributor to Unicode

KSP2 is still patched conics. Also here's a free n-body mod made by modders, https://github.com/mockingbirdnest/Principia

Principia - 𝑛-Body and Extended Body Gravitation for Kerbal Space Program

But one should just be aware that KSP simplifies by only tracking the strongest source of gravity. This turns all orbits into actual ellipses. But there is a mod called Principia that replaces it with the proper thing, thus allowing for very chaotic (but cool) flight paths using less thrust.

Principia has n-body

Install Principia and Real Solar System, then try again :P

Theres a mod that changes that to N-body simulation, it's called Principia

I'd suggest looking at their readme: https://github.com/mockingbirdnest/Principia

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/