I recently presented two sessions at xRMVirtual on building resilient integrations using Polly and Simmy with Dynamics 365.

You can watch the recording of the first session here:

https://365.training/Player/index/xrmvirtual/af60c4f2-a32e-eb11-a813-000d3a58ba85

Here’s the recording for the second session:

https://365.training/Player/Index/xrmvirtual/9c0b82f0-208b-eb11-a812-000d3a58b5ae

I would highly recommend going through the following links to develop a better understanding of various resilience strategies and learn about design patterns and anti-patterns as well.

Azure Transient Faults:

https://docs.microsoft.com/en-us/azure/architecture/best-practices/transient-faults
https://blog.jonathanoliver.com/idempotency-patterns
https://docs.microsoft.com/en-us/azure/architecture/patterns/throttling
https://docs.microsoft.com/en-us/azure/architecture/patterns/retry
https://docs.microsoft.com/en-us/azure/architecture/patterns/circuit-breaker
https://docs.microsoft.com/en-us/azure/architecture/best-practices/retry-service-specific

Anti-Patterns:

https://docs.microsoft.com/en-us/azure/architecture/antipatterns/improper-instantiation

Dynamics 365 API Limits:
https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/api-limits-overview
https://docs.microsoft.com/en-us/power-platform/admin/api-request-limits-allocations
https://docs.microsoft.com/en-us/powerapps/developer/common-data-service/api-limits

Polly:
http://thepollyproject.org
https://github.com/App-vNext/Polly

Simmy:
http://thepollyproject.org/2019/06/27/simmy-the-monkey-for-making-chaos/
https://github.com/Polly-Contrib/Simmy

Notable Tools/Frameworks:
https://github.com/dastergon/awesome-chaos-engineering#notable-tools
https://dev.to/azure/serverless-circuit-breakers-with-durable-entities-3l2f
https://netflixtechblog.com/making-the-netflix-api-more-resilient-a8ec62159c2d

Must Watch:
Mastering Chaos – A Netflix Guide to Microservices
System Stable: Robust connected applications with Polly, the .NET Resilience Framework – Bryan Hogan

Leave a Reply

Your email address will not be published. Required fields are marked *