swift-distributed-actors VS Orleans

Pretty exited for this. Looks like a good alternative to Erlang or Akka with the native performance / low resource utilization of Swift. Erlang lacks strong typing and Akka is DSL-hell.

Looks like they've open-sourced a transport [0] and are adding support for distributed tracing as well [1, 2], which is a huge aid for system operators and debugging.

[0] https://github.com/apple/swift-distributed-actors/

Apple is in the business of selling hardware, and developing a cross-platform toolkit would have to potential to cannibalize that. I think Swift's weak footing in other OSs is also owed to that fact.

Apple's best bet is to create an ecosystem of hardware and software that is self-sustaining and moated. I'd argue that they are successful in that, but all those web platforms have significantly weakened the moat. You don't need apps like Sketch anymore (infact I consider Figma way superior), and you don't need most of their bundled native apps anymore (their are great replacements that are either native or web based).

So how will they strengthen the moat? Certainly not by further weakening it by sharing code with other platforms. They seem to be ready to accept that distributed systems won't go away and are obviously actively buying into that space (https://github.com/apple/swift-distributed-actors/). But, UI-wise, I'm only seeing renewed determination to push native apps: https://www.imore.com/apple-rebuilding-apple-music-native-ap.... And I think it makes sense for their bread-and-butter hardware business.

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