The doc predates ACID transactions support in Orleans, but it talks about the Virtual Actor model vs the Akka model in general.
At the end of the day, I think Orleans and Akka are conceptually different types/notions of what an actor framework is.
> Orleans uses a different notion of identity than other actor systems. In other systems an “actor” might refer to a behavior and instances of that actor might refer to identities that the actor represents like individual users. In Orleans, an actor represents that persistent identity, and the actual instantiations are in fact reconcilable copies of that identity.
A virtual actor is very similar to an entity in Akka that is running in cluster sharding and uses Akka persistence. It's just that it's not packaged up into the virtual actor concept by default. I would love Akka to provide a more hand-holding more Orleans style module to be honest, it's a great concept and way to think about systems :-)
With Akka you manage objects actively, much like memory in C, with Orleans your objects behave much like normal Dotnet/Java objects, they are just distributed and must use async methods. Orleans adds a layer of management, where it will tear down and re-instantiate objects as required, distributes them in the cluster, etc. As a programmer you don't have to worry about it, it's all managed by the runtime.