aka "Going towards total vendor lock in by basing your system on a proprietary, non portable infrastructure service"
BTW: I really hate the marketing inventions. There's no cloud, or serverless, you still run your software on someone's server.
Anyway the serverless is essentially (as someone here pointed out) the same idea as shared hosting which is very popular with php. It just uses a different name.
Check out Serverless https://github.com/serverless/serverless . It'll work for Lamba, google cloud, Azure, and IBM Whisk
If you look at AWS's own framework Chalice https://github.com/awslabs/chalice it basically has you import Chalice where you would otherwise import flask, making it fairly easy to switch to hosting yourself later if you want.
I choose a preinstalled distro, deploy my script to automatically handle dependencies and set up the container infrastructure, pull the containers, and I have a server set up and able to run my containers in about 3 minutes, and connected to a central server so it can be provisioned containers to run.
The entire infrastructure can obviously be moved to another hoster in days, because the hoster is just providing a machine.
hmm, not if the only thing you have to do it upload an image on a server, there is nothing difficult with it. And yes the vendor lock in is a big deal unless all you write is throw away code. But it looks like it's the purpose of "Serveless servers", throw away apps ...