Orleans – Distributed Actor Model
github.com
Orleans – Distributed Actor Model
1–10 of 21 posts
Re: Orleans – Distributed Actor Model
#2https://groups.google.com/forum/#!topic/akka-user/C0WGdTs2gy...
"One other thing is that the way these entities are presented to the user is via static nominal interfaces, which precludes the kind of freedom an Actor shall have according to the model (technically it also fails on the count that actors can create other actors, so it only implements message passing and misses actorOf() and become()). Therefore I would not call it an implementation of the Actor Model."
http://www.infoq.com/news/2014/07/approaches-actor-model-net
"Sergey answered by claiming that Become is just one way of reading the definition and therefore not a requirement of the actor model."
PS: having been burnt with WPF and XNA, I would rather go with Akka.NET:
1) not likely to die;
2) cross-VM (CLR, JVM);
3) based on the "standard" interpretation of the Actor Model.
Re: Orleans – Distributed Actor Model
#3https://groups.google.com/forum/#!topic/akka-user/C0WGdTs2gy... "One other thing is that the way these entities are presented to the user is via static nominal interfaces, which precludes the kind of freedom an Actor shall have according to the model (technically it also fails on the count that actors can create other actors, so it only implements message passing and misses actorOf() and become()). Therefore I would…
I get what you are saying... I'm just wondering why you feel burned by WPF. They've recently announced that it will be under active development for many years to come. Granted, they've announced new application models, but they haven't abandoned WPF.
Akka.net has been developed as open source for longer and benefits greatly from that, but Orleans is open source and is being used by internal teams at MS...im not sure how that really compares to the uses of akka, but its not really "abandonware".
Re: Orleans – Distributed Actor Model
#4If I understand correctly, this product is similar to AKKA. But it's c# implementation and target to windows users or mainly windows users.
Re: Orleans – Distributed Actor Model
#5Does anyone have any insight into how Orleans handles failure? The only mentions I found in the documentation suggest that "grains cannot fail", which seems fairly odd to me. What about exceptions? Can grain state become corrupted? How does the system recover? Is there anything like Erlang's links or monitors here? Are supervisors relevant at all in this system?
Re: Orleans – Distributed Actor Model
#6Does anyone have any insight into how Orleans handles failure? The only mentions I found in the documentation suggest that "grains cannot fail", which seems fairly odd to me. What about exceptions? Can grain state become corrupted? How does the system recover? Is there anything like Erlang's links or monitors here? Are supervisors relevant at all in this system?
There was a build 2014 session on how it works...it was pretty in depth. The video is on channel 9.
Re: Orleans – Distributed Actor Model
#7Does anyone have any insight into how Orleans handles failure? The only mentions I found in the documentation suggest that "grains cannot fail", which seems fairly odd to me. What about exceptions? Can grain state become corrupted? How does the system recover? Is there anything like Erlang's links or monitors here? Are supervisors relevant at all in this system?
There was a build 2014 session on how it works...it was pretty in depth. The video is on channel 9.
I couldn't find the original but this gets into it a bit:
Using Orleans to Build Halo 4’s Distributed Cloud Services in Azure http://channel9.msdn.com/events/Build/2014/3-641
Re: Orleans – Distributed Actor Model
#8Curious how the interfaces required in Orleans compare to typed actors coming in Akka 3.0
Re: Orleans – Distributed Actor Model
#9https://groups.google.com/forum/#!topic/akka-user/C0WGdTs2gy... "One other thing is that the way these entities are presented to the user is via static nominal interfaces, which precludes the kind of freedom an Actor shall have according to the model (technically it also fails on the count that actors can create other actors, so it only implements message passing and misses actorOf() and become()). Therefore I would…
I get what you are saying... I'm just wondering why you feel burned by WPF. They've recently announced that it will be under active development for many years to come. Granted, they've announced new application models, but they haven't abandoned WPF. Akka.net has been developed as open source for longer and benefits greatly from that, but Orleans is open source and is being used by internal teams at MS...im not sure…
Some .NET devs tend to separate WPF from the XAML stack.
Personally I never though of myself as having WPF skills, rather XAML stack skills.
All the concepts, XAML, bindings, MVVM, ... are applicable to WPF, Silverlight and Metro, even if the APIs are a little different.
Re: Orleans – Distributed Actor Model
#10Microsoft has another active & mature project aimed at simplifying concurrency heavy applications. Its called TPL DataFlow [1].
It gives you simple & intuitive primitives which you can use to build higher level abstractions (one of them is actor model)
1. https://msdn.microsoft.com/en-us/library/hh228603(v=vs.110)....