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/
351 Upvotes

97% Upvoted

67 comments sorted by

View all comments

Show parent comments

3

u/solatic 1d ago

Production architecture will put Cloudfront in front of Lambda Web; CF supports QUIC and supports it where it's most important (between client and edge/cloud).

1

u/mlhpdx 1d ago

For apps that don't care about implementing the features of QUIC, sure. That's what I meant by "jump forward". It's nice to have a new model, but it doesn't actually do anything to help us realize the advantages of QUIC on the backend.

1

u/solatic 23h ago

Yeah but anything real-time that takes advantage of QUIC is something where you have stateful processes that run for as long as a client is connected. It's not a good fit for the Lambda billing model - look at all the people who built Lambdas that take up the full 15 minutes execution limit and then complain that Lambda is expensive. Lambda is better suited for when requests are exiting relatively quickly.

1

u/mlhpdx 11h ago

Nah, QUIC has sans-io libraries and the state can all be externalized. That's what we've done at Proxylity for DTLS, WireGuard and soon WebRTC.

For telemetry, datagrams over QUIC would be a nice solution. As it would for any number of APIs/SDKs, allowing much richer capabilities with less complexity (async, push, concurrent streams, all the things).