On Wed, May 14, 2014 at 1:13 PM, Alexandru Nedelcu <[email protected]>wrote:
> Hi, > > Just noticed project > Orleans<http://research.microsoft.com/en-us/projects/orleans/>, > which is like an actors implementation for .NET, still in preview I think. > It’s supposed to be higher-level than Akka, the description being: > > It is actor-based, but differs from existing actor-based platforms by > treating actors as virtual entities, not as physical ones. First, an > Orleans actor always exists, virtually. It cannot be explicitly created or > destroyed. Its existence transcends the lifetime of any of its in-memory > instantiations, and thus transcends the lifetime of any particular server. > Second, Orleans actors are automatically instantiated: if there is no > in-memory instance of an actor, a message sent to the actor causes a new > instance to be created on an available server. An unused actor instance is > automatically reclaimed as part of runtime resource management. An actor > never fails: if a server S crashes, the next message sent to an actor A > that was running on S causes Orleans to automatically re-instantiate A on > another server, eliminating the need for applications to supervise and > explicitly re-create failed actors. Third, the location of the actor > instance is transparent to the application code, which greatly simplifies > programming. And fourth, Orleans can automatically create multiple > instances of the same stateless actor, seamlessly scaling out hot actors. > > Any thoughts? > -- > Alexandru Nedelcu > www.bionicspirit.com > > PGP Public Key: > https://bionicspirit.com/key.aexpk > I saw a presentation on Orleans on the Microsoft Tech Days. It looked interesting at first glance, and does something very different with actors compared to what Akka does. There is no concept of an ActorRef for example, and no stopping, starting or watching actors, supervision or child actors. The lifetime management of the actors is completely under control of the framework: From what I understood, the only thing you can do with an actor is send a message to its well-known identity, or a thin wrapper around the well-known identity. This will take care of actor creation if it doesn't exist. --Martijn > -- > >>>>>>>>>> Read the docs: http://akka.io/docs/ > >>>>>>>>>> Check the FAQ: > http://doc.akka.io/docs/akka/current/additional/faq.html > >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user > --- > You received this message because you are subscribed to the Google Groups > "Akka User List" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/akka-user. > For more options, visit https://groups.google.com/d/optout. > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
