Orleans: Microsoft's distributed systems framework for .NET

[@gamedev_expert]

The rebalancing feature is absolutely amazing! Thanks for all your hard work.

[@aL3891_]

i really wish the docs where updated with these new features, getting started with them now is not very easy

[@XKS99]

I just finished a small project using Orleans. Didnt need the 'distributed' capability although in the future it might come in handy. The Orleans actor model implementation is just awesome and so easy to wrap your head around. What I am wary of is how much extra overhead the code generation imposes on a large scale application.

[@ivaniliev93]

great presentation, great team, in discord the guys are always helping as well, what a time to be a developer I would say

[@hello-jonas]

is the video description copy paste from aspire? :-)…

[@daveanderson8348]

People are getting lazier and lazier

[@devashishdalvi7527]

Yo!😂

[@JonGalloway]

Sorry about that! With over 90 videos edited and posted less than a week after the conference ended, we're bound to make a few mistakes. Fixed.

[@duongphuhiep]

5:43 when the Green request hits the first instance (S1), how did it know that Green had been already cached in (S2) then try to get it from S2 instead of the Database? I doubt that all the overhead of discovery for where Green was cached (S2) then asked (S2) to return it to be expensive. Maybe more expensive than the traditional stateless pattern with a cache layer.

[@duongphuhiep]

Great video though, mixing the distributed cache with the services instances themselves is a very interesting technique

[@emmanueladebiyi2109]

Amazing work 🙌🏽