Exactly. What if amazon decides to close your account, because you know.. they can. Now you're pretty much screwed.

With traditional VPS you just point ansible/salt/puppet to new servers and you're good to go.

Ironically this happened to me due to a card expiry fuck up.

Same thing happened to me. Card got expired but they wouldn't let us add a new card (or payment method as they call it) because the account was in some invalid state. When asked what it was, they couldn't give the details due to legal reasons.

It took about 2 months with support (Business support) and finally they chose to close the account.

We created a new account with a new card and migrated our AWS infrastructure. Unfortunately we still have to use AWS..for now.

Yeah, that's what I think too. This feels too far into the vendor-lockin, downtime death zone, as reliable as Amazon might be.

Plus, while it might be cool for some microservices, it seems like it would be a lot more unwieldy trying to do a full scale application.

Or as App engine decided to do, increase prices/decrease quotas. What now? rewrite your code or just pay the new prices.

Lambda functions are just Docker containers.

API Gateway could be replaced by something like Open Resty.

S3 can be replaced by any other file storage solution.

And language lock-in. So far Lambda supports only Node.js and Java.

Java gets you ruby via JRuby and Python via Jython... (Not sure how current they are these days). So missing C and Rust type stuff I guess?

The AWS Lambda team wrote a blog post about how to use Python - https://aws.amazon.com/blogs/compute/using-python-in-an-aws-...

You can also call native binaries so you therefore you can use languages like Go or C or anything else that statically compiles.