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)
Interesting new concept of the library. Gonna look how the new http extensions package looks like, in most cases I prefer adding policies (strategies) when registering http client as factory in DI. The important thing to mention: Polly v8 doesn't need a Wrap to combine policies, it combines them automatically. And othe order is FIFO instead of FILO in Wrap policy in v7
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.
@@MilanJovanovicTech I just found this video, a circuit breaker would be awesome, especially in a microservice architecture, when for example you have a lot of messages to process and you are relying on an external API that can fail, so instead of only retrying we should stop trying for a specific time. Looking forward to this content in the next video ;) BTW another useful video. Thank you!
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...
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 🎉
@@MilanJovanovicTech Question is: should you even mock the policies? I'd say no. Because in reality you want to test the scenario where the code fails for which you use the polly pipelines
