dataverse

We have an integration between Dataverse and a third party system that runs in Azure Functions. Third party have now acknowledged that in certain race conditions their system can create two entries duplicated on what should be a unique key. Just deployed what I hope is a fix to our code that uses blob lease distributed locking via the madelson/DistributedLock library… #

A short reflection on the Dataverse resilience tests so far #

A fourth approach to parallel record creation in Dataverse using HttpClient with retry logic from Polly #

A third approach to parallel creation in Dataverse using HttpClient without any retry logic (naive starting point) #

A second approach to parallel record creation using ServiceClient but using Parallel.ForEachAsync #

I try a naive approach to parallel record creation using ServiceClient and example code from the documentation. #

A collection of notes exploring how to make applications that rely on Dataverse more resilient #