61–70 of 287 posts
I'm a core developer on Orleans. Feel free to ask any questions here, or on gitter: https://gitter.im/dotnet/orleans I gave a talk recently on how we use it at Microsoft: https://www.youtube.com/watch?v=KhgYlvGLv9c - the talk is very short and so it does not go into many details, but it gives an overview of some internal use cases.
Why is it called orleans?
Earlier quoted context omitted.
Academically (And, to some extent, practically speaking) Orleans Virtual actors aren't the same as Erlang (or Akka) actors. Major differences: - Normal actors are pretty flexible, can work in local or remote contexts. Orleans is probably best described as Sharded Actors, It's a 'guided' implementation of Actors compared to Erlang or Akka where you are given a toolkit and have to build out what you intend to do. - Orl…
> - Orleans doesn't have any ordering guarantees. While this is not a firm requirement of the Actor model itself, both Erlang and Akka guarantee ordering between a given Sender-receiver pair (i.e. messages sent from A to C will be sent in order) I thought Erlang only guaranteed that if the processes are on the same node. Is that not correct?
http://erlang.org/faq/academic.html#idp33052176
http://erlang.org/pipermail/erlang-questions/2017-September/...
Dang could you https that? It works fine.
EA/BioWare created an equivalent for some of their online services on the JVM: https://github.com/orbit/orbit
I wonder, what would it be worth to the world if there were an actor framework for multiple languages that offered interopability between languages? IIRC Akka.net and Akka aren't compatible with each other.
EA/BioWare created an equivalent for some of their online services on the JVM: https://github.com/orbit/orbit
I wonder, what would it be worth to the world if there were an actor framework for multiple languages that offered interopability between languages? IIRC Akka.net and Akka aren't compatible with each other.
It supports all languages that compile to wasm.
Very early stage project, though.
Earlier quoted context omitted.
I'm also one of the core developers of Orleans. Ironically, I recently joined Temporal. There are definitely some similarities, but also major differences between the models, especially when it comes to the execution model and fault tolerance.
Since you're an expert on both, do you mind discussing which of the two you like better? And the reasons behind it?
I'm a core developer on Orleans. Feel free to ask any questions here, or on gitter: https://gitter.im/dotnet/orleans I gave a talk recently on how we use it at Microsoft: https://www.youtube.com/watch?v=KhgYlvGLv9c - the talk is very short and so it does not go into many details, but it gives an overview of some internal use cases.
Maybe I'm looking in all the wrong places, but I'm having a surprisingly hard time finding hardware requirements. I love that with Erlang I can throw an experimental app on Digital Ocean for just $5/mo and see if it gets traction. How much more resource intensive is Orleans and what kind of resource usage should I expect as I scale up the number of actors?