Already know a little about Microsoft Orleans and want to know how to persist grain state in AWS DynamoDB, watch this video: th-cam.com/video/q8nFqQ-8wLw/w-d-xo.html
Great intro video! I have one question: At 8:09 you said "Make sure this grain can be communicated across the cluster even though the cluster is local now." Does that mean communicate the grain between different silos? What does cluster mean here?
Grains belong to a silo. You can run multiple silo's on the same set of machines if you really wanted to - but that's unlikely to happen in practise. So here, cluster essentially means the same as silo - a group of machines. Without looking, I think what I meant by local is that the grain client and the grains were running on the same machine, essentially forming a cluster of 1 machine. In reality it would be a load of machines and everything would be split out everywhere :) HTH
Thanks Stu, I found this a useful watch and I look forward to seeing more. Are you planning on going a bit deeper in the series? A contrast between the virtual actor model and traditional n-tier architecture would be good to see.
There are more up in the series now in case you haven't seen them :) I'll consider doing an architecture video once we've completed the journey into AWS
Hello, thanks for your video, it helps us a lot, sorry my English is not very good. I have a problem, I am trying to follow your example in VS for Mac v 8.10.21 and when I install the microsoft orleans NuGets, when executing the project (This is without altering the project created at startup by VS, that is, without creating HelloWorld), it only loads in the browser. I did tests and apparently it has to do with the Orleans NuGets, because if I uninstall the project it runs fine. Am I missing something that I need to configure from Orleans?
I was able to solve the problem by installing the same version of the packages v 3.3.0 I haven't investigated why, but with v 3.6.0 it wasn't working for me and it didn't show an error either.
Great video! Just subscribed. Do you know how to get it working with .NET 5? Followed your steps with only difference of choosing net5 as targetframework, but got compile errors from the orleans codegenerator package. After switching to netcoreapp3.1 it worked.
Found out what my problem was, I installed Microsoft.Orleans.OrleansCodeGenerator.Build instead of Microsoft.Orleans.CodeGenerator.MSBuild. After changing to the MSBuild package it worked fine with .NET 5
Unfortunately I did not realise how small it would render on some devices until I published. I have definitely corrected this over time as I learn more about how TH-cam does stuff on different devices and which publish settings need to be set properly
for me, I need to see that something works (and has easy integration to my existing project) b4 I investing hours into it. for a zero-level orleans user like me, it think it is solves those 2 problem... the explanation he gave at the beginning shows its a lot more than this... I'm off to a more indepth video but i'm fine with this as an intro!
Already know a little about Microsoft Orleans and want to know how to persist grain state in AWS DynamoDB, watch this video: th-cam.com/video/q8nFqQ-8wLw/w-d-xo.html
Excellent! Is very simple and practice. Thank for share! Regards of the Argentina. 😃
Great intro video!
I have one question:
At 8:09 you said "Make sure this grain can be communicated across the cluster even though the cluster is local now."
Does that mean communicate the grain between different silos?
What does cluster mean here?
Grains belong to a silo. You can run multiple silo's on the same set of machines if you really wanted to - but that's unlikely to happen in practise. So here, cluster essentially means the same as silo - a group of machines. Without looking, I think what I meant by local is that the grain client and the grains were running on the same machine, essentially forming a cluster of 1 machine. In reality it would be a load of machines and everything would be split out everywhere :) HTH
Great Video, The best one out there. But unfortunately I still do not understand what is orleans and what is used for exactly ?
Because all examples of Orleans is about Hello World application. Who wants to scale that? Begging for a practical real world scenario example.
Thanks Stu, I found this a useful watch and I look forward to seeing more. Are you planning on going a bit deeper in the series? A contrast between the virtual actor model and traditional n-tier architecture would be good to see.
There are more up in the series now in case you haven't seen them :) I'll consider doing an architecture video once we've completed the journey into AWS
why have you added the grain in DI? Because in Controller constructor you have used ClusterClient.
@codeWithStu, how come a transient grain is keeping counter, which is state private to grain, in between different requests when you do refresh?
do grains compare to pods in Kubernetes? Is it like a pod, but instead of a server, it's an actor object?
Hello, thanks for your video, it helps us a lot, sorry my English is not very good.
I have a problem, I am trying to follow your example in VS for Mac v 8.10.21
and when I install the microsoft orleans NuGets, when executing the project (This is without altering the project created at startup by VS, that is, without creating HelloWorld), it only loads in the browser. I did tests and apparently it has to do with the Orleans NuGets, because if I uninstall the project it runs fine.
Am I missing something that I need to configure from Orleans?
I was able to solve the problem by installing the same version of the packages v 3.3.0
I haven't investigated why, but with v 3.6.0 it wasn't working for me and it didn't show an error either.
Thanks for letting me know - glad you got it sorted :)
Great video! Just subscribed. Do you know how to get it working with .NET 5? Followed your steps with only difference of choosing net5 as targetframework, but got compile errors from the orleans codegenerator package. After switching to netcoreapp3.1 it worked.
Found out what my problem was, I installed Microsoft.Orleans.OrleansCodeGenerator.Build instead of Microsoft.Orleans.CodeGenerator.MSBuild. After changing to the MSBuild package it worked fine with .NET 5
Great to know, I'm sure this will help others out as well! Thanks!
The use of tiny fonts in the Visual Studio parts of the presentations greatly limit their value.
Unfortunately I did not realise how small it would render on some devices until I published. I have definitely corrected this over time as I learn more about how TH-cam does stuff on different devices and which publish settings need to be set properly
Choice of the example project is poor. Nobody understands the real world benefits of Orleans from Hello World example.
for me, I need to see that something works (and has easy integration to my existing project) b4 I investing hours into it. for a zero-level orleans user like me, it think it is solves those 2 problem... the explanation he gave at the beginning shows its a lot more than this... I'm off to a more indepth video but i'm fine with this as an intro!