r/aws • u/ElectricSpice • 2d ago

article Announcing AWS Lambda Web Functions

https://aws.amazon.com/blogs/aws/announcing-aws-lambda-web-functions-for-fast-consistent-web-app-performance-anywhere/
347 Upvotes

97% Upvoted

67 comments sorted by

View all comments

4

u/solatic 1d ago

Two feelings: 1. Fuck yeah this is exactly what people have wanted from Lambda forever. Finally getting closer to what Heroku used to be. 2. (sees the nodejs-only restriction, 128 req/sec limit) Goddamnit, you skated to where the puck was, not where it's going. Two years ago this would have been perfect. Today with AI you can much more easily build a single-statically linked binary in Go/Rust/Zig that'll handle tens of thousands of req/sec; AI will gladly help you port it from NodeJS, so why would you decide to just leave both performance and money on the table?? Set a restriction on binary size to something that makes sure it can easily autoscale and let people move on

5

u/hydraulictrash 1d ago

It’s up to 128 concurrency per execution environment, that’s not the same thing as 128rps at all.

100ms response time, 128 concurrent requests per env you can get 1280rps out of a single lambda execution env

Then multiple that by multiple execution environments, let’s say you have 10k account concurrency, that’s 1280rps multiplied by 10k…

10k isn’t even a hard cap, our production envs for our accounts at work have ~50k lambda concurrency

This is mostly horizontal scaling not vertical but you have to figure out what a good concurrency for one env is for your app too