Orleans VS CSLA .NET

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

I've heard (no first hand experience) that the csla .net framework is meant to address this particular problem https://cslanet.com/. Rocky did an interview on dotnet rocks and it seemed like a tool worth looking into.

Put your blazor components in its own project (Visual Studio Razor component library) and you can then use them from either Blazor server or WASM. I've been doing that along with using CSLA which really makes it simple to switch from one to the other. CSLA itself has somewhat of a steep learning curve, bit you should be able to get a general idea of how to setup you project for not server and WASM from their Blazor example.