Cloud Computing Without Containers

Re:Cloud Computing Without Containers by luddy on Friday November 09, 2018 @02:50PM (#18417324)

The article says that pushing a new lamda@edge function takes 30 minutes. That has not been my experience. I routinely push lambda@edge versions from the AWS console and the new versions typically run within a minute or so. Have others seen anything like a 30 minute propagation delay?

[ Parent | on HN ]

Re:Cloud Computing Without Containers by zackbloom on Friday November 09, 2018 @07:44PM (#18419225)

Lambda@Edge is built on Cloudfront and pushing any change to Cloudfront generally takes 20-30 minutes in my experience. Can you tell me more about the change you're making? Is it code or config changing?

[ Parent | on HN ]

Re:Cloud Computing Without Containers by luddy on Saturday November 10, 2018 @08:56AM (#18421337)

I'm talking about using the Lambda@edge console to push a new, numbered version of a lambda function written in node.js. I have pushed 100s of versions in this way, and I would guess that the mean time until the new version begins running is on the order of one minute. By "begins running", I mean that the new version number appears in CloudWatch output.

No other changes to config.

[ Parent | on HN ]

Re:Cloud Computing Without Containers by jtokoph on Friday November 09, 2018 @02:54PM (#18417363)

I haven’t used lambda@edge but I have used lambda. Lambda deploys almost instantly from my experience.

[ Parent | on HN ]