[flagged]
Until it does and then you are screwed without an easy way to get out if your application is anything else than trivial. It has it's uses; a simple page/site which won't get any users and a system that needs to elastically scale forever, but in between, you are just burning (your company) money for no reason other than HN said it is the best (a lot of people here are working at FAANG; it's baffling why anyone would take any advice from architecture ran at a company with 100k more employees than their own startup with all this cloud / devops garbage and resulting costs and headaches).
One setup I’ve used with a previous client was deploying many FastAPI lambdas, wrapped in Mangum. You can even in the same code base expose both. This way, you can deploy to a container and a lambda without changing any code.
In one case, we used APIGWv2 to give the lambda an HTTP endpoint, in the other, it’s the container that provides it. You can throw in IPv6 support by having a CF distro in front of both.
I share the frustration though and the article resonated with me. I'm currently working on a project that's being inappropriately done in cloud functions, and it's just dumb. We'll never scale beyond a few hundred users, but there's a load of considerations and hoop jumping we'd have completely skipped if the org had stayed off the Kool Aid.