Robust Connected Applications with Polly, the .NET Resilience Framework

Want to see how to make your applications much more resilient and reliable with just a few lines of code? With Polly, the .NET resilience framework (a .NET Foundation project), your application can easily tolerate transient faults and longer outages in remote systems or infrastructure. Come see how Polly can make your application a rock solid piece of work.

[@CarlHamilton1914]

This is perfect. Our dev lead asked us to research using Polly for adding retry logic to one of our micro services and this is exactly what I was looking for.

[@PatelKunalR]

very well explained. thanks a lot

[@ronzhong]

Can we use Polly with Blazor WebAssembly to make client-server API calls?

[@bryanhogan5643]

Yes :)

[@baharalirezaei3608]

how can we share the state in circuit breaker ?

[@stoppanigiovannino]

hi, I would like to know where Polly persists data relating to queued requests

[@yp5387]

I was wondering that too..

[@reneschindhelm4312]

I don't think it does other than in-memory. Polly with its rather nice syntax and implemented patterns/policies will help you with the actual act of sending requests over the network or other kind of unreliable transports. It helps you by not having to re-invent the wheel (see the naive implementation starting at 1:55) and reducing the complexity in your program's code base.
In the end, you need to keep track of the overall state of a request on your own. You could store the state of a request in a database or message queue. Think about what will happen when your program would crash or gets stopped while sending a request and waiting for a response and how to defend against it. You need your program to pick up where it left off. That's not what Polly's about.

[@bryanhogan5643]

In the case of the Bulkhead Isolation policy, it is in local memory.