[movedx]

Just because you've never had to overcome or experience the problem, it doesn't mean it doesn't exist.

If you've ever had to develop an MVP from the ground up and build a business around it, services like this are critical to your acceleration, time to market, and budget.

[stefantheard]

that's why I said "or non obvious" I'm not totally sold on this saving time but I guess it could be argued depending on the expertise of the developer

[movedx]

> depending on the expertise of the developer

The more experienced the developer, the faster they are. The faster the technology enables you to be, the faster you'll produce something. Both go hand in hand.

An experienced developer would absolutely love Serverless for most problems they face. Having the option of doing as little Ops as possible and just solving problems in software is the very definition of a software developer (which certainly might be changing over time) :)

[stefantheard]

I still don't see where the savings of time come in. What you lose in "ops" you gain in configuration and assuming you don't have eidetic memory that has a time cost.

[movedx]

What configuration? I use AppEngine for a personal project I'm developing, and besides the app.yml file, which is about five lines long, I don't configure a thing. In fact, I don't even have to stand up databases to use one: I just make the API call to store the data and it's handled for me. Literally zero configuration.

That's in the standard environment. Even in the Flexible Environment the configuration is equally nonexistent.

Give AppEngine a try: I honestly believe you'll consider it the true definition of Serverless.