How Microsoft Orleans can save .NET Developers from microservices

Microsoft Orleans is the future of building distributed applications on the C# and .NET stack and you don't need to worry about building a grand microservices architecture to use it.

0:00 Intro
0:21 What is Microsoft Orleans?
1:58 What is a grain in Microsoft Orleans?
2:57 How you can get the benefits of microservices using the Orleans actor model instead
4:32 Why Microsoft Orleans is important
5:48 Comparing the future of Orleans with .NET MAUI
6:47 Team behind Orleans
7:23 Outro

#csharp #dotnet #microservices

[edandersen]

Opinions in this video should be taken with a grain of salt, I am just a balding .NET boomer. Thanks for watching 🙏

[gingerbreadman]

Absolutely 💯 we opted for Orleans over Microservices on an Enterprise application which scales like crazy. It's amazing. We also wrote it in F# because it better suit our needs as a mature product.

[bradygaster]

awesome video. i said the same thing you're saying after building a cloud native demo using all the buzzwords. i looked at Reuben and said "you know it would have been 10x easier and run faster had i just built it with Orleans." liked and followed! keep up the spice!

[isaiahnelson]

Yes, more videos please on Orleans. Been trying to get more traction on its adoption at my corp. You provided a succinct explanation of Orleans relevance. I am particularly interested in the JournaledGrains and understanding how to leverage them to replay to current state or past state for a front end.

[aargomemnon]

Thanks for the video. What could get it to the next level is block diagrams, animation, small code samples and a good mic to capture the sound quality.

All the best for the next one.

[Funkbassfushion]

Some valid points about small teams/companies wrestling with the complexity of microservices. I've seen developers immediately defaulting to using docker without really considering the implications of that decision.

[JonPerson]

Thanks for the video! I'd love to see an example of how an existing .NET Core microservice class would be refactored into Orleans to get an idea what the end result looks like.

[kmogathal]

You are a Robin Hood mate in the world of Microsoft 😅
Absolute legend.
Glad someone else too feels the same for MAUI ❤.

[mtwguj]

Doesn’t Orleans do what Akka .net can do? Or did I get this wrong?

[michaelmsm]

Orleans is great, but I don't think it is accurate to say that you no longer need devs who understand infrastructure and DevOps, or Docker and Kubernetes. Orleans still has to be deployed somewhere and supported in production, and k8s is a valid choice.

[kidservice]

Thank you, this is very interesting. Could you make a more in depth analisys of pros and cons of the two approaches and show some examples of Orleans? Also I do not completely agree with MAUI. It is half a disaster now (too many bugs, too many features missing from Xamarin), but, since it is the only replacemente for Xamarin, unless Microsoft wants to completely abandon mobile development they will keep it alive and improve it for a long time.

[simonegiuliani]

Like your agnostic takes on things. Enough of those MVPs.

[sigma_z]

This is AMAZING video and yes, Microsoft Orleans videos please. Thank you. Btw, is it me, or is the sound terrible in this video?

[Ocean]

Hey Ted 👋, love your content. What road map would you recommend to a junior dev looking to one day become an mvp like yourself

[ArkFen]

With all respect cannot agree about MAUI = new Silverlight. Two reasons at least. Silverlight death is connected not to MS support (or its absence) but to the new restrictions in the modern browsers and because of that stopping things like Flash, Silverlight and similar which were using underline obsolete technology. MAUI on the other hand is always convert your code to the native code of the OSs where you want to use your app... so even if some restrictions, safety regulation or OS itself has major changes, we also change MAUI and that's it and that's all - there is not strict dependencies and calling things MS or .NET and support of Microsoft (which in most cases aways more and longer than needed) has nothing to do with that. Same is true about Blazor (just mentioning it here because I heard some folks comparing it with Silverlight as

[RedHotBagel]

Man, a highpass-filter on your audio wouldn't hurt.

[LeviRamsey]

JVM folk can do the same thing with Akka.

[managed-code]

we gave up on microservices long time ago and switched to Orleans.
I have no desire to go back =)

[pxnchx]

This sound so good, but man what a bad name 😆