We use Lambda for ETL type work, Healthchecks, Web Scraping, and infrastructure automation.
> Serverless makes it harder to test locally, harder to move between hosts
Most of our code is written in Java. We have a main method, which calls a static method. The only difference between running locally and running in Lambda is that the Lambda calls the static method while we call the Main method locally.
This also pretty much eliminates lock-in since all of the code behind the static method could without much trouble be moved behind an API endpoint running in a more traditional environment.
> The only ones that should be considering serverless are companies that need to scale up and down operations at a moment's notice. That is if you're huge or doing a lot of short-burt big data processing. Otherwise, it's all koolaid.
Respectfully disagree, as first hand experience has taught me otherwise.
Just like any tool, Lambda is extremely effective when used for the things it excels at.
The number of others using it at the same time has no bearing on price.