I'm sure 'serverless' has a good time and place to be used, but in my experience it has just always been the worse choice.
"But we need to be able to scale!"
Sure, but we're not in a place where we're getting anywhere near early mySpace / Facebook / Google style growth. Just get a regular ass cheap VPS and stick your service on it; if you need to expand upgrade the VPS. If it's starts getting serious then let's look at compartmentalizing and distributing it if we need to.
https://health.aws.amazon.com/health/status
I suspect the big problem is that IAM (AWS authentication system) is affected and it is not decentralized, which is causing other systems worldwide to fail because the internal authentication is broken.
I can't login to the AWS console to check on my stuff in the European zone, because the login goes through IAM in us-east-1 where all the authentication does.
It really highlights just how centralized so much of the internet is on like three companies (Amazon, Microsoft, and Google)
https://health.aws.amazon.com/health/status
I suspect the big problem is that IAM is affected and it is not decentralized, which is causing other systems worldwide (even outside of AWS' us-east-1 location) which rely on IAM in us-east-1 to also fail. I'm having trouble even logging into the AWS console to check on my European servers.
Edit: IAM is the main authentication method. So AWS may still be up and running fine in other locations around the world; but if you can't connect to them because AWS' internal authentication is all fucked up...
Absolutely. People really sleep on just how much traffic a simple low end server running a PHP framework can handle. I've ran systems with a million users (combined across multiple domains and clients but still) and it was just fine with a single database server and a few web servers. They would have needed to hit the tens of millions of users before serious refactoring or rewriting would have ever been necessary to consider.