Would have liked to see some real cost analysis, other than it should save you money, because that is only true if scale is small to medium. That's the thing,

Would have liked to see some real cost analysis, other than it should save you money, because that is only true if scale is small to medium. That's the thing, I guess the demographic that lambada is going for it will save money, but along with the mentioned vendor lock in, when you really need to have something on and processing requests non stop the costs savings really evaporate. It's weird to me that the serverless thing catches on when it seems to be best suited for projects in their infancy without need for 24/7 request processing , or things out of the critical path like image resizing or things of this nature. But entire apps? Feels very much like going back in time to shared hosting. I could see it saving money until about 1m requests a day and then a sharp drop off where you are hemorrhaging cash after that... With modern auto scaling systems that aws and gce provide I bet most shops don't stand to save any more money than with a normal modern day refactor. At the end of the day this leaves you more rope to hang yourself with. It makes it easier to run slow or poorly thought out code. 1000 processes might be cool but is never as cheap as 2 working correctly that accomplish the same thing, as an extreme but actual example of a situation I helped unwind with GAE, which was serverless before the buzzword.