Earlier quoted context omitted.
How long would you like it to be? Chris Munns - Lead of Dev Advocacy for Serverless@AWS
Make it indefinitly and price exponentially. ;)
thar be dragons :)
AWS Lambda pricing now per ms
171–180 of 291 posts
Re: AWS Lambda pricing now per ms
#172Earlier quoted context omitted.
> ...we really want you to be able to pay for what you use. Cloudflare Workers has the right pricing model. They only charge for CPU time and not wall time. They also do not charge for bandwidth. > Lots of sub 100ms workloads... AWS Lambda (or Lambda at Edge), as it stands, is 10x more expensive for sub 50ms workloads (Workers does allow upto 100ms for the 99.9th percentile) that can fit 128MB RAM. https://medium.com…
Except that none of the rest of your infrastructure is there, and that APIs represent just a non-majority part of Lambda workloads.
It's nice to get a semi-official confirmation of AWS pricing strategy: create lock in, then overcharge.
Re: AWS Lambda pricing now per ms
#173This means that using bigger CPUs (by allocating more RAM) just became even more important.
That was my first thought. Over a lot of the curve it's almost free to run on a bigger slice. When you get down to just a few billing quanta the math didn't work out in your favor.
Re: AWS Lambda pricing now per ms
#174Earlier quoted context omitted.
> ...we really want you to be able to pay for what you use. Cloudflare Workers has the right pricing model. They only charge for CPU time and not wall time. They also do not charge for bandwidth. > Lots of sub 100ms workloads... AWS Lambda (or Lambda at Edge), as it stands, is 10x more expensive for sub 50ms workloads (Workers does allow upto 100ms for the 99.9th percentile) that can fit 128MB RAM. https://medium.com…
Except that none of the rest of your infrastructure is there, and that APIs represent just a non-majority part of Lambda workloads.
Yet, if you're a Cloudflare user, all of your edges are there - so it doesn't matter. We use Workers extensively for
"edge" related things. Lambda, never - but for working with S3 buckets, sure. They feel similar, but differently specialized.
Re: AWS Lambda pricing now per ms
#175Earlier quoted context omitted.
I don't think they are doing it to be nice to consumers. I think they are doing it to cost less than competitors.
Are you implying that they are trying to make money?
I'm implying that they are trying to undercut competition to drive them out of business so they can then raise prices across the board.
Re: AWS Lambda pricing now per ms
#176Anyone 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.
How long would you like it to be? Chris Munns - Lead of Dev Advocacy for Serverless@AWS
I have many workloads where 15 minutes may be just a little too short for comfort. A hour timeout would have me reaching for Lambda more often.
Re: AWS Lambda pricing now per ms
#177Is there a way to use lambda where I can use ffmpeg to watermark and downscale a 4K video? Possibly some system where I can throw a lot of computing at the job and get it done quickly. Right now on my vps it takes multiple minutes to get done and scaling up the vps for one feature or dedicating another server for it is overkill.
I'd check out Amazon Elastic Transcoder (https://aws.amazon.com/elastictranscoder/).
Re: AWS Lambda pricing now per ms
#178Earlier 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.
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.
Re: AWS Lambda pricing now per ms
#179All 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 and sleep much better (and at lower maintenance cost).
Re: AWS Lambda pricing now per ms
#180Earlier 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"?
This is pretty standard AWS marketing spiel. They make vague assertions of "ah but you're not considering the big picture...." with no details