> Yeah, I took a look at using a serverless framework for a hobby project, and it was just a real pain to get started at all, let alone develop a whole application in.

Look into Firebase functions. Drop some JS in a folder, export them from an index.js file and you have yourself some endpoints.

> exports.helloWorld = functions.https.onRequest((request, response) => { response.send("Hello from Firebase!"); });

The amount of work AWS has put in front of Lambdas confuses me. Firebase does it right. You can go from "never having written a REST endpoint" to "real code" in less than 20 minutes. New endpoints can be created as fast as you can export functions from an index.js file.

And if you need a dependency that has a sub dependency with a subdependency that uses a native module prepare for poorly defined -fun- hell getting it to work. A surprising amount of standard is libs do.

*standard js libs (as in commonly used)

Eh, you win some you lose some.

Being able to throw up a new REST endpoint in under 10 minutes with 0 config is really cool though.

And Firebase Functions are priced to work as daily drivers, they can front an entire application and not cost an insane amount of $, per single ms pricing. Lambda's are a lot more complicated.