In case it helps Terraform users estimate their cloud costs, I updated https://www.infracost.io to support the new ms-based Lambda pricing ( https://github.com/infracost/infracost/pull/248/files , it'll be in the next infracost release). I'm interested to hear what people think about https://www.infracost.io/docs/usage_based_resources - longer term we could extend that to fetch average_request_duration from cloudwatc…
AWS Lambda pricing now per ms
261–270 of 291 posts
Re: AWS Lambda pricing now per ms
#262Earlier quoted context omitted.
To be clear, you're acknowledging Cloudflare has a much better pricing model but just not as many other services yet?
They're not easily comparable (I tried using Cloudflare Workers before going back to AWS). Lambda@Edge runs Node or Python. Cloudflare Workers runs V8 with "worker isolates" which has a few more caveats, an imperfect but improving dev experience, and doesn't work with a lot of npm packages.
Re: AWS Lambda pricing now per ms
#263I wonder if this change will push more people to consider rewriting code to more memory and CPU-efficient programming platforms, for example from java/c# to C or Rust?
I thought you are limited in the languages they permit, the fastest of which being Go.
https://aws.amazon.com/blogs/opensource/rust-runtime-for-aws... https://docs.aws.amazon.com/lambda/latest/dg/runtimes-custom...
Re: AWS Lambda pricing now per ms
#264Were lots of memory tiers (eg. 256MB) removed? They aren't present on pricing page anymore.
Re: AWS Lambda pricing now per ms
#265Earlier quoted context omitted.
No to be clear I'm saying you are comparing things that are way more different than our friends at Cloudflare would like you to think. They aren't brought up in any of the convos I have with customers.
> No to be clear I'm saying you are comparing things that are way more different than our friends at Cloudflare would like you to think. Care to expand on that? What exactly do you mean by "things are way more different"?
On Lambda you get a full environment inside an OS container. On CloudFlare you get a WASM process.
The Lambda model is more compatible which can be a real benefit.
Re: AWS Lambda pricing now per ms
#266Earlier quoted context omitted.
Yep, but I prefer to care about manually fetching data from SQS. It's a weird system, but due to our data model there are many benefits to processing as many messages in a given lambda as possible.
This might be useful to simplify that model for you :) https://aws.amazon.com/about-aws/whats-new/2020/11/aws-lambd...
Re: AWS Lambda pricing now per ms
#267Necessary change. Now writing stuff in fast languages suddenly matter in cost, changing the landscape of when these solutions might become viable for a chase.
thats ok they will slow down some random dependency to compensate for their loss
Re: AWS Lambda pricing now per ms
#268Earlier quoted context omitted.
What would be really useful for my use case (running browser tests on a schedule) is if Cloudflare workers actually supported running full headless chromium automation in addition to just V8 isolates. Right now I'm using puppeteer/playwright + Lambda, but would love to have more options.
CloudWatch Synthetics may fit your usecase? https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitori... Then there are more specialized browser-testing providers like LambdaTest.com and BrowserStack.com
Re: AWS Lambda pricing now per ms
#269Earlier quoted context omitted.
Okay, nice. And if I would like like 32 vCpus? Having an application today that has a huge degree of parallelism, but utilizing an external cloud provider that offers dedicated machines with very affordable pricing. Would really like to use lambdas instead though.
Interesting. Not possible today. We'd still encourage paralyzation up through multiple concurrency of functions being executed.
Re: AWS Lambda pricing now per ms
#270Necessary change. Now writing stuff in fast languages suddenly matter in cost, changing the landscape of when these solutions might become viable for a chase.
And you can pick any language you'd like as it supports arbitrary containers now too: https://news.ycombinator.com/item?id=25267182