Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

AWS recently (prematurely) announced lambda function URLs, which would make API Gateway unnecessary [1]. It will probably be officially launched in the next couple of weeks.

For our app, I'm in the process of removing API Gateway and calling lambdas directly from our back end servers instead, as it added a lot of complexity and the 30 seconds timeout imposed by API Gateway is causing issues.

1. https://www.reddit.com/r/aws/comments/qxrubv/lambda_function...



I tried API Gateway -> Lambda but found it a bit too complex to even setup.

Instead, I've used ALB -> Lambda (1) to good effect; much simpler to setup and no maintenance issues so far.

(1) https://aws.amazon.com/blogs/networking-and-content-delivery...


ALB integration limits payload size to 1Mb, compared to 6Mb one gets with Lambda API or API Gateway. I would love to use ALB more, if not for this limit.


Finally! This has been a glaring omission for me for years and has prevented me from adopting Lambda thus far.


Is this different va what Google already does this Cloud Functions?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: