[johansch]

Well, Google App Engine (both the standard/classic and flexible kinds) has been and still is pretty awesome for people who don't want to worry too much about SRE stuff but still not pay through the nose.

AWS Lambda just seemed like too much bureaucratic busywork for no good reason (ugh API Gateway...), last time I tried it out.

I guess it maybe appeals to "enterprise" type developers? Maybe it this way cause Werner Vogels is german and from an academic background? :-) I'm adventurous, because I write this knowing that even referring to national characteristics results in instant down votes here.

Just give me an endpoint where I can respond to HTTP requests and parse the URL path/parameters myself, thank you. That way I can keep it as simple or as complex as is needed, per situation. I just don't want to bother with your insanely over-engineered API of definining custom API requests.

[flowardnut]

>Just give me an endpoint where I can respond to HTTP requests and parse the URL path/parematers myself, thank you.

This would be "lambda proxy"with api gateway. Happy to post code samples or whatever.

You can also specify via slightly watered down regex what controller is called, and even do "nothing matched go here"configuration

it's clunky, it needs work, but it's been great for crud or utility stuff

[michael_l_650]

Yeah I don't use the AWS much, how does this different from GAE? Hasn't GAE existed for a while already? I feel like it's always had it's uses, and it's very nice! But the revolution didn't happen five years ago, don't see why it would happen now.

[johansch]

The difference is that Lambda is a) way more annoying to use, b) gets way more coverage, because developers are locked into the AWS ecosystem and often don't pay the bills.