Now the same thing has got another stupid name: Serverless. I wonder what the same stuff will be called two years from now.
What has changed is that the suite of services now exist to fully enable an application to be (almost) completely serverless.
Similar to micro-services, people will overuse the word and it will seem like a fad. IMO, it's more than a fad. Once the toolchain is mature, it will become the default way of building applications.
Web 3.0 is truly serverless because your application lives on a decentralized p2p cloud.
Ethereum/Swarm(or IPFS)/Whisper is an example of a serverless p2p stack.
You may as well call the service they're selling "managed", because that's what it is.
When "cloud" or "serverless" will be cheaper than managing your own dedicated servers, then it will actually be useful. Until then, it's just marketing.
* how many real or virtual servers are running your code.
* how the servers were provisioned or setup.
* how to access the servers (either via SSH or programmatically), either than through predefined APIs.
* what happens when the servers break.
* what causes the servers to disappear.
* etc.
The "server" concept has been abstracted out of the equation and you're no longer required to think in terms of servers. (there is one exception: RAM usage is still something you need to predict for AWS Lambda.)
Instead, you're thinking in terms of limitations and usage of the service.
With the above said, serverless has a bit of journey to make. The toolchain is growing and the workflow of local development, testing and deployment is still a work in progress. I feel like it's a great time to jump in because there is a lot of exciting work to do and a good foundation to build on top of.