Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AWS Lambda pricing now per ms

aws.amazon.com

Post reply on HN
Print view View original

211–220 of 291 posts

Re: AWS Lambda pricing now per ms

#211

Post by alisonkisk »

munns wrote: post #101
mrits wrote: post #96

Earlier quoted context omitted.

To be clear, you're acknowledging Cloudflare has a much better pricing model but just not as many other services yet?

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.

This comment would be much more useful if you gave some clear examples of the difference (presumably something you get on Lambda that makes it worth more per ms than Cloudflare).

Otherwise it's just "AWS said, Cloudflare said"

Re: AWS Lambda pricing now per ms

#212

Post by alisonkisk »

jrd259 wrote: post #178
ignoramous wrote: post #106

Earlier quoted context omitted.

But you're telling us that Lambda's prices are justifiably higher because of the strong vendor lock-in? AWS is starting to sound more like Oracle. Ironic. :) Besides the fact that Cloudflare's part of the Bandwidth Alliance with GCP and other infrastructure providers from which AWS is conspicuously absent, Cloudflare's also slowly but surely building a portfolio of cloud services.

This reply is in bad faith. He did not attempt to "justify" the pricing with "vendor lock-in". Indeed, the prices went down, not up.

The question here isn't the price change here (which is in some sense mainly about balancing short functions and long functions, removing the penalty for short functions) , it's where the pricing is at overall vs Cloudflare.

Re: AWS Lambda pricing now per ms

#213

Post by akh »

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 cloudwatch or datadog.

Re: AWS Lambda pricing now per ms

#214

Post by Lord_Baltimore »

irrational wrote: post #74
trisiak wrote: post #32

Earlier quoted context omitted.

Isn't that the same in practice? You get customers by being nice to them. Being nice to customers means competitive pricing, high quality support, good documentation, easy integration, etc. It's all driving towards the same goal.

It's not necessarily the same in outcome. Undercutting competitors can be a temporary thing. As soon as the competitors are eliminated you jack the prices up. Doing it to be nice to customers can potentially last even after competitors go belly up. Then again, Google's motto used to be "do no evil" (basically be nice to customers). That obviously went the way of the dodo bird.

>>As soon as the competitors are eliminated you jack the prices up

And then you provide a competitor or startup another opportunity.

Re: AWS Lambda pricing now per ms

#215

Post by diegocg »

jimmaswell wrote: post #162
catchmeifyoucan wrote: post #2

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.

How many people actually use lambda? Always came off as a gimmick to me.

They can seem not that useful by themselves. Their power comes from the integration with the rest of AWS services.

Re: AWS Lambda pricing now per ms

#216

Post by hbbio »

kadukeitor wrote: post #95

I think now is a good time to use this kind of services. https://callbackfy.com It's essentially a way to save some money by avoiding long http requests by buffering requests and sending a callback when the result is complete.

Using a service with a TLS certificate error... probably not.

Re: AWS Lambda pricing now per ms

#218

Post by munns »

austinpena wrote: post #209
munns wrote: post #169

Earlier quoted context omitted.

The naming is a bit of a misnomer, today L@E doesn't run at the edge (in our PoPs) but when you deploy it copies to every region and then CloudFront routes you to the lowest latency region for your request.

So is L@E multi region then? Like if I have two concurrent requests across the globe are they serviced from two locations?

Yes, but you deploy it from one region.

Re: AWS Lambda pricing now per ms

#219

Post by YuriNiyazov »

munns wrote: post #56
catchmeifyoucan wrote: post #2

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.

Awesome! That was the idea here. Lots of sub 100ms workloads and we really want you to be able to pay for what you use. - Chris, Serverless@AWS

Hey Chris. Happy to see your awesome trajectory from Meetup admin to The Serverless AWS guy.

Re: AWS Lambda pricing now per ms

#220

Post by hbbio »

koluna wrote: post #179

All fine and dandy, until it is not. Lambda = massive vendor lock-in, which means once you start depending on it, it’ll be hard to rip it out of your system and replace with someone else. My startup used to heavily rely on Lambda and frankly I wish we never did - so much AWS-specific complexity that is just not worth the trouble. Their own representative admits it[0]. We moved everything to containerized workflows an…

We use λ with Go and the change between the service and its λ counterpart is really minimal.

FYI, we're using https://github.com/awslabs/aws-lambda-go-api-proxy which supports most Go web frameworks.

Edit: We also use DynamoDB and there lies the real vendor lock-in with AWS imho.

Post reply on HN