I don't get the comparison between Orleans and .NET MAUI. They're two different beasts. MAUI makes it convenient to code UI and functional elements that can target multiple platforms with minimal changes to the codebase.
Thanks for the comment. It's more about comparing the long term viability of the two frameworks after so many people have been burnt by jumping on the wrong horse. I believe Orleans has legs because MS use it themselves.@@elcheapo9444
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.
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!
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.
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.
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.
Hey thanks for the comment. Depending on the interest I'll look at doing a pros/cons vid 👍 Agree on MAUI. My point is that I don't think the A Team is on it any more and in a world where even MS use web tech for desktop UI it's probably a bit past it's time.
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.
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.
I am not and will likely never be a Microsoft MVP lol As a junior developer I would get experience with TypeScript and Python at the moment. Combine those with C# and you'll get decent coverage.
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 well)))))
I meant that I think MAUI is going to share the fate of Silverlight. Abandoned and with a load of projects out there stuck on it. You would have to be total koolaid drinker to use at this point in my opinion - just like you had to be to use Silverlight at the time. When non Microsoft teams are doing a better job (Avalonia, Uno etc) at the concept it's saying something.
Don't give up on the idea of microservices. Remember that these concepts are just conceptual tools that you can use. You want to use the right tool in the right place. Not every app should be some microservice ecosystem and not every app should be some monolith. Sometimes you should have multiple databases and sometimes you really should just have one. Every scenario is different and different tools can make your life easier in different scenarios.
@@pxnchx93 Bear in mind that Orleans was probably an internal code name for this as it has been in use internally at MS way before they probably thought of open sourcing it. So marketing didn't get to them on time.
Opinions in this video should be taken with a grain of salt, I am just a balding .NET boomer. Thanks for watching 🙏
I don't get the comparison between Orleans and .NET MAUI. They're two different beasts. MAUI makes it convenient to code UI and functional elements that can target multiple platforms with minimal changes to the codebase.
Thanks for the comment. It's more about comparing the long term viability of the two frameworks after so many people have been burnt by jumping on the wrong horse. I believe Orleans has legs because MS use it themselves.@@elcheapo9444
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.
I can imagine a really fun place to work, combining Orleans with F#
I like, I like. F# F# F# F# F#!!!!
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!
Long time bro, I miss you from the Charlotte Days
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.
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.
trufax
What are the implications?
@@michaelmsm89I'm here wondering what downsides come with containers. I've experienced zero downsides with containers.
You are a Robin Hood mate in the world of Microsoft 😅
Absolute legend.
Glad someone else too feels the same for MAUI ❤.
Haha, cheers.
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.
Hey thanks for the comment.
Depending on the interest I'll look at doing a pros/cons vid 👍
Agree on MAUI. My point is that I don't think the A Team is on it any more and in a world where even MS use web tech for desktop UI it's probably a bit past it's time.
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.
There is a code sample on the corresponding blog post: tedstech.com/why-microsoft-orleans-is-important-for-net-developers/
Like your agnostic takes on things. Enough of those MVPs.
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.
Yep. I should have been more clear but you don't need them to be experts. Focus on the software.
Nice one Ted. Love the glasses.
Cheers Howlkun
This is AMAZING video and yes, Microsoft Orleans videos please. Thank you. Btw, is it me, or is the sound terrible in this video?
Thanks and its not just you, the sound is terrible in this video :-) Turn the subs on heh.
Man, a highpass-filter on your audio wouldn't hurt.
Yep
Hey Ted 👋, love your content. What road map would you recommend to a junior dev looking to one day become an mvp like yourself
I am not and will likely never be a Microsoft MVP lol
As a junior developer I would get experience with TypeScript and Python at the moment. Combine those with C# and you'll get decent coverage.
Ok thanks. Can I get your twitter handle? I’d love to have a productive conversation with you on there from time to time
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 well)))))
I meant that I think MAUI is going to share the fate of Silverlight. Abandoned and with a load of projects out there stuck on it. You would have to be total koolaid drinker to use at this point in my opinion - just like you had to be to use Silverlight at the time.
When non Microsoft teams are doing a better job (Avalonia, Uno etc) at the concept it's saying something.
Doesn’t Orleans do what Akka .net can do? Or did I get this wrong?
yes but it’s easier
💯
we gave up on microservices long time ago and switched to Orleans.
I have no desire to go back =)
Don't give up on the idea of microservices. Remember that these concepts are just conceptual tools that you can use. You want to use the right tool in the right place. Not every app should be some microservice ecosystem and not every app should be some monolith. Sometimes you should have multiple databases and sometimes you really should just have one. Every scenario is different and different tools can make your life easier in different scenarios.
JVM folk can do the same thing with Akka.
Yep
This sound so good, but man what a bad name 😆
Better than a forced acronym like "MAUI" imo
@@edandersen Service Weaver is cooler, no?
@@pxnchx93 Bear in mind that Orleans was probably an internal code name for this as it has been in use internally at MS way before they probably thought of open sourcing it. So marketing didn't get to them on time.
@@edandersen Right that's what I thought, sound much more like Project Orleans