Great content!

amazing , no words to thank you

@cloudwithraj

3 жыл бұрын

Most welcome Vishnu 😊

Thank you.... A 1000 times!

all your contents are to the point and very well explained, like this one, and please keep doing your interview prep Q&A it also helps alot. thanks Raj bhai you rock \m/

@cloudwithraj

2 жыл бұрын

Thanks brother 🙏

very informative, thank you!

@cloudwithraj

2 жыл бұрын

Glad it was helpful!

Thank you, that was very informative.

@cloudwithraj

3 жыл бұрын

Glad it was helpful!

Just found your channel. Excellent Content. Another sub for you sir!

@cloudwithraj

Жыл бұрын

Awesome, thank you!

Thanks much. Quite detailed and informative content. How about the micro services perspective of comparing these services? For instance, the feature set and cross-cutting concerns that ECS/EKS provides along with service mesh, in managing/governing MS cluster would be better than with Lambdas. Can’t this also be a decision influencer?

Great video ! 10:40 Does this mean that when a new concurrent invocation of my function happens, Lambda will provision the new instance in a different AZ, or does it mean that every Lambda function runs with HA under the hood and invocations are load balanced across those 3 underlying instances (which would be in contradiction with your statement saying that Lambda will provision a new instance for every new concurrent invocation) ? I believe it is the former, rights ? In that case it would work as follows: 1) 1st time the function is being invoked =>it is provisioned in AZ1 2) a new concurrent invokation happens => a new lambda instance is provisionned in AZ2 3) the first invocation is over, but a new invocation occurs => that invocation is routed to the instance in AZ1

The only drawback of this kind of comparison is that it deprives us from a reality of vendor-locking matter, the more you're reliant on cloud-native rather than Kubernetes, the more trouble you'll encounter later when you by any chance to move out

I guess it all comes down to the cost factor and performance to choose which technology to use. As far as I know if lambda memory is below 1.8GB, it has only 1 vCPU which may not suitable for computing intensive task which requires multi-processing. but again, increasing the memory also means more cost

@AnhNguyen-vu7mc

3 жыл бұрын

also in order for lambda to access a resource in a VPC, it will create an ENI. if there are a lot of requests coming in, a lot of ENIs will be created which may fill up IP address reservation in a subnet

2 questions - 1. can an EKS fargate be triggered by SQS 2. How can i scale up EKS fargate based on the SQS events and not based on CPU/Memory metrics

@cloudwithraj

3 жыл бұрын

There is no direct way to trigger EKS Fargate from SQS. You can do SQS triggering Lambda, that Lambda calling the Load Balancer fronting EKS Fargate.