21–30 of 291 posts
Anyone know why there's a hard limit of 15 minutes for Lambda (and 9 minutes for Google Cloud Functions)? Still seems really weird to me.
For reference - Lambda functions used to billed at 100ms intervals. My Node.Js function usually only takes 37-40ms to run. So this is a pretty good advancement for cost savings.
Earlier quoted context omitted.
Why only for some people? It always rounded up to 100ms. If your function took 101ms, it was billed as 200ms.
If it takes 60 seconds, that's 600 steps. 601 steps isn't that much of a saving. It matters close to 0.
I've learned that AWS pricing tends to improve over time, and I appreciate it. I just recently switched from a startup offering authorization to AWS Cognito because the startup kept raising their price(s). It's nice to see this drop, though I'm sure Amazon does it due to competition as well.
It's nice to see that AWS is using their economy of scale to reduce their own costs, and passing that on to the consumer.
I am curious to see if this will mean a shift to more efficient languages (Go or Rust) for Lambda services, as usually people default to JS
Earlier quoted context omitted.
Why only for some people? It always rounded up to 100ms. If your function took 101ms, it was billed as 200ms.
If it takes 60 seconds, that's 600 steps. 601 steps isn't that much of a saving. It matters close to 0.
Earlier quoted context omitted.
It's nice to see that AWS is using their economy of scale to reduce their own costs, and passing that on to the consumer.
I don't think they are doing it to be nice to consumers. I think they are doing it to cost less than competitors.
It's still great to see.
I've learned that AWS pricing tends to improve over time, and I appreciate it. I just recently switched from a startup offering authorization to AWS Cognito because the startup kept raising their price(s). It's nice to see this drop, though I'm sure Amazon does it due to competition as well.
It’s an interesting model because apps either optimize for or happen to fall into “loopholes” where some customers end up getting more value than others or may turn into a financial liability at scale.
For example, think about authentication... charging per auth will mean that some use cases will be nearly free, as some external users may only sign in once per quarter. But charging a flat rate has the opposite effect. You have to design the service and tweak the metrics and rates to make it work.