AsyncEx VS Orleans

PS: You may want to look at the other in-memory concurrency structures available. You may find something that perfectly fits the specific problem you are trying to solve. https://learn.microsoft.com/en-us/dotnet/api/system.threading?view=net-7.0, https://learn.microsoft.com/en-us/dotnet/api/system.collections.concurrent?view=net-7.0, and https://github.com/StephenCleary/AsyncEx

Async Lock.

If you haven't seen it before, there's an excellent async util library on nuget by Stephen Cleary called Nito.AsyncEx.Coordination. It contains a number of classes to help with async synchronization, giving options beyond SemaphoreSlim. It might be worth checking out.

and if you need ReaderWriterLock behavior in an async context, Stephen Cleary has an implementation

Pessimistic concurrency - you can use something like AsyncLock from Nito.AsyncEx package, to lock around each db access.

This library has class that will allow you to safely run async code in Sync-context enabled environment.

Nito.AsyncEx:

We should chat more about Reminders v2 - I want to learn more about what you'd like it to provide. Can you comment on the issue (https://github.com/dotnet/orleans/issues/7573)? If you'd like to see some of what is in the works, please message me on Discord and we can chat more about it (https://aka.ms/orleans/discord)

for ADO scripts config, I ran the main, clustering, and persistence scripts but got runtime error lacking some migration sql object (don't remember the exact error message). But after some debug, I had to run this extra migration script which was not mentioned in that ADO config page.

I think Orleans is going to introduce something similar that Temporal has on .NET 8 https://github.com/dotnet/orleans/issues/7487

Something tells me that the developers should have cleared batchOperation a bit later. Judging by the fix, the Orleans developers agree with me.

Dapr is created for multi language purpose. If you have only .NET Stack there is mature and more faster Microsoft Orleans. Debugging is easy with local silo - just debugging the same process.

There are some more perf improvements coming to Orleans serializer, like this 1.6x improvement to message serialization: https://github.com/dotnet/orleans/pull/8185