No offense, but this sounds exactly like the experience I had, and many friends had, before we actually learned how to use the service. If I had to guess, you're using the smallest possible 128MB config and not calling it very often. This presents a maximally-bad first experience for devs by Amazon but is not reflective of how it works once you get some actual utilization happening. All that said I moved to containers on Azure for unrelated reasons. But Lambda works fine (within its obvious architectural restrictions) and they'll hold your hand for a $49/month developer service plan fee.