The Brand New Way to do Fault Handling in Polly V8

The Performance Improvement is literally impressive (mainly 0 allocation)

Poly is a library for handling resilience and transient errors that allows developers to use policies like retry, circuit (execution) blocking, timeout, bulkhead isolation, and fallback in a thread-safe manner in a Fluent style.

Retrying and timeout handling are patterns that can be used frequently in source code. Other restore-related features provided by poly include

Retry 7 / Retry: Allows you to configure automatic retries.
Circuit-breaker 7 / Circuit-breaker, circuit (execution) blocking: Block execution for a certain amount of time if an error exceeds a threshold.
Timeout 1 / Timeout : If a timeout occurs, we will not wait any longer.
Bulkhead Isolation: Restricts controlled operations to a fixed-size resource pool so they don't impact other areas.
Cache 1 / Cache: Use cache to automatically store and make responses available.
Fallback / Fallback: Returns a fallback value or executes the action on failure.
PolicyWrap 1: Allows you to flexibly combine the above policies.
Poly is powerful and stable enough that you can try it out via the quickstart link above and start applying it to your code right away.

This library has been featured on dotnetdev in the past, but it's so useful that I'm reintroducing it in the .NET Foundation Project Introduction.

great video, Milan. Your explanations are always top-notch. Thank you and keep up the good work!

Impressive video.

How about unit Testing an Mocking the new Poly plicies in your code?

As I was introduced to this kind of technique for the first time by this video, I just wonder what is the performance benefit over try-catch.

Using magic strings is always something that worries me.
"How many refs does your di-pipeline-provider have / is it used at all?". [Ctrl]+[Shift]+[F] to the rescue 😖
"Great, no compile errors" ... Runtime steps in and alerts you about a typo in your magic string 🎉

Could you please make a video on best practices with sample examples on exception handling in mvc core applications

Is it just me or the new builder stuff seems a step back?
I mean, it probably would benefit some complex policy composition, but for simpler policies seems to be an awful lot of additional code needed to have the same result.
Performance improvements are impressive, though...

Way to complicated

I've been playing around with this new version for a few hours now, and it's much easier to grasp then the previous version. Could you have a go at a video on the Dynamic Reload functionality? I think it would be good to see that in action for concurrent rate limit, retry and circuit breaker options.

The syntax has become too verbose.

Great

is AddResiliencePipeline scope or transient?

Great video, thank you very much.

Please make a video on latest
Microsoft.Extensions.Resilience library

Bro, your content is amazing. This is the second time I've needed to figure out how to use new library, and you help me with this. Thanks!) Keep doing this way)

In a clean architecture, where is the best place to put resilience strategies? in endpoints, applicatio layer, infra?

I am switching to this ASAP. Thanks for sharing.

excellent work.

over confusing. Static version was lot easier

Amazing content! Thanks Milan for your sharing.