Thanks again for these videos Sir. I was just wondering how these ec2 Instances in the Target Group are different from Worker Nodes that are scaled in a kubernetes cluster?
Great question... I think the difference is on the granularity that makes up one application instance. In this video, each EC2 instance in the target group is build from an AMI an is a single purpose virtual machine that contains full application stack. So one EC2 instance = one application instance. The kubernetes cluster contains master and worker nodes that can host many individual containers (pods). In this case one pod = one application instance. So each k8 worker node is "general purpose" and can hose many applications or many instances of the same application. Another way to think about this is that the auto-scaling group in this video is scaling at the "infrastructure level" and the k8 is scaling at the "application level". You obviously could add more workers to the k8 cluster to scale the k8 infrastructure. In the end, either way works. I have some videos coming out on orchestration using docker swarm, kubernetes, and their managed versions in AWS (ECS, EKS). Hopefully those will also highlight the differences between the approach in this video and orchestration at the application / service level.
@@thetechnologysandbox Very many thanks again Sir. I will certainly be looking forward to the videos that explain the difference between the 2 approaches
Halo Sir! do you have a space or time to assist individuals on a paid service? i want to deploy my website on aws via Laravel forge. can you assist me please!
Sorry @samahnation, I do not have the time to offer anything like that. I do use forge to deploy to Digital Ocean. It seems pretty straight-forward, but I know deploying to AWS might be different. If I recall, their help at forge was pretty responsive.
![POLYCAT - ข้อความรูปยิ้ม [Music Video]](http://i.ytimg.com/vi/lBhIgPGCgbI/mqdefault.jpg)
Could we possibly explore scaling in different AWS regions?
Thanks again for these videos Sir. I was just wondering how these ec2 Instances in the Target Group are different from Worker Nodes that are scaled in a kubernetes cluster?
Great question...
I think the difference is on the granularity that makes up one application instance. In this video, each EC2 instance in the target group is build from an AMI an is a single purpose virtual machine that contains full application stack. So one EC2 instance = one application instance. The kubernetes cluster contains master and worker nodes that can host many individual containers (pods). In this case one pod = one application instance. So each k8 worker node is "general purpose" and can hose many applications or many instances of the same application.
Another way to think about this is that the auto-scaling group in this video is scaling at the "infrastructure level" and the k8 is scaling at the "application level". You obviously could add more workers to the k8 cluster to scale the k8 infrastructure.
In the end, either way works. I have some videos coming out on orchestration using docker swarm, kubernetes, and their managed versions in AWS (ECS, EKS). Hopefully those will also highlight the differences between the approach in this video and orchestration at the application / service level.
@@thetechnologysandbox Very many thanks again Sir. I will certainly be looking forward to the videos that explain the difference between the 2 approaches
Halo Sir! do you have a space or time to assist individuals on a paid service? i want to deploy my website on aws via Laravel forge. can you assist me please!
Sorry @samahnation, I do not have the time to offer anything like that. I do use forge to deploy to Digital Ocean. It seems pretty straight-forward, but I know deploying to AWS might be different. If I recall, their help at forge was pretty responsive.
@@thetechnologysandbox thank you!