Because Lambda/Cloud functions are meant for scripting tasks in your cloud environment, not for building full-fledged apps.
(Lambdas couldn't even be triggered with HTTP calls when AWS Lambda launched.)
(Lambdas couldn't even be triggered with HTTP calls when AWS Lambda launched.)
I'm a massive fan of AWS Lambda, but using it to serve public API quests is just a nightmare. Just because you _can_ do something, doesn't mean you should.
I'm constantly puzzled by why people use Lambda for this - if you don't want to deal with managing traditional services, there's plenty of other options out there (in AWS and otherwise) that are much more suited to the task of serving a website.
I generally really like AWS and I use it for a ton of stuff, but I very much welcome competition and innovation in this space.
Google Cloud Functions is a lightweight, event-based, asynchronous compute solution that allows you to create small, single-purpose functions that respond to cloud events without the need to manage a server or a runtime environment.
Where is the reference to scripting?
"...single-purpose functions that respond to cloud events..."
They are meant to react to events within your infrastructure, rather than being public facing application endpoints.