Hello @everythingwhatyouwanttokno2488 , thanks for note. I tend to disagree and think it's on case basis. Yes, I understand Sagemaker endpoint is very popular, but if ECS, and EKS work, then there is no limitation on why lambda can not work. In case of ECS and EKS, you need to have the task running all the time (unless using fargate), where as if you are using the same docker container image for Lambda or ECS, it shouldn't matter. You can always keep Lambda function warm using a ping call from an event bridge scheduler. Serverless is a paradigm shift. Please do share if you have any case where ECS/EKS work but lambda with container doesn't work. The only limitation I can see is 15 mins timeout for lambda and 29 seconds for API gateway to Lambda integration. But if any use case for prediction is making a user wait for more than 29 seconds on browser (Or 15 minutes to lambda function url) then it should be more async integration for such cases. it would take similar long time to respond from Sagemaker / ECS /EKS end points as well. Thanks
Really good content
I am glad you like it, Thanks!
In real world lambda don't work ecs ,eks or sagemaker endpoints
Hello @everythingwhatyouwanttokno2488 , thanks for note.
I tend to disagree and think it's on case basis. Yes, I understand Sagemaker endpoint is very popular, but if ECS, and EKS work, then there is no limitation on why lambda can not work. In case of ECS and EKS, you need to have the task running all the time (unless using fargate), where as if you are using the same docker container image for Lambda or ECS, it shouldn't matter. You can always keep Lambda function warm using a ping call from an event bridge scheduler.
Serverless is a paradigm shift.
Please do share if you have any case where ECS/EKS work but lambda with container doesn't work. The only limitation I can see is 15 mins timeout for lambda and 29 seconds for API gateway to Lambda integration. But if any use case for prediction is making a user wait for more than 29 seconds on browser (Or 15 minutes to lambda function url) then it should be more async integration for such cases. it would take similar long time to respond from Sagemaker / ECS /EKS end points as well.
Thanks