[el_dev_hell]

I use the serverless framework for simple REST APIs. This is especially beneficial if you're hooking into other cloud provider tools (such as S3, SQS, ect. with AWS).

The main reason is speed of deployment and overhead. I can push the code to a repo and boom -- a working backend with basically no infra config.

I've found this works very well for internal glue tools that aren't majorly affected by cold starts.

One nice example was building a quick and dirty internal tool for L3 support staff to alter certain client records. It wasn't appropriate to hand out DB access and it wasn't a high enough priority to create a new feature in our "real" support system, so I build a few basic endpoints (with strict rules) and passed it off to the team. They're using Postman to make the changes as needed (using a JWT for auth from our main application).