AWS feels like hosting on IIS back in the day. It was extremely expensive and pointless for more than 50% of their customers, but people kept saying “but we’re enterprise!” and throwing money away until the world finally woke up.
AWS feels like hosting on IIS back in the day. It was extremely expensive and pointless for more than 50% of their customers, but people kept saying “but we’re enterprise!” and throwing money away until the world finally woke up.
Where AWS really comes into is stuff like serverless (yeah, I hate that term too), auto-scaling, object storage, etc. I've got a few static sites that are compiled in AWS Code Build whenever I push new markdown to GitHub (literally just using shell scripts and pandoc). They're then pushed to S3 and sat behind CloudFront. It costs me a few dollars a month to host, I don't need to think about scaling and I get near instant page load times. Running that kind of thing on-prem wouldn't even come close to being as cheap nor convenient as AWS.
This is why I commented about WP being ill-suited for modern cloud deployments in my edit.
To be clear, I'm not claiming AWS are the only hosting providers to offer the aforementioned. The same arguments can be made for and against GCP, Azure and so on and so forth. I'm also not advocating that everyone should switch away from WP or adapt their workloads for the cloud. People should just use what works for them the best. I'm only commenting on why that AWS architecture isn't as insane as it first appears.
You need this complexity in an enterprise environment because the web teams don't have access to databases, and the DBAs aren't allowed to manage databases outside of the data network, etc. That's why enterprise content management exists. Big companies and public sector value repeatability and seperation of duties over cash and time.
12F apps, microservices, etc. are much _cheaper_ to run on AWS because you don't have to worry about scaling/provisioning/and HA/DR capabilities are basically baked in. A lambda that processes 100,000 requests/day is, on average from the teams I've worked with, significantly cheaper to run than a machine in a DC that is always up.
I used to unequivocally scoff at "the cloud", but I used to think it was "MySQL as a service" or "VMs as a service" when it is able to be so much more with cloud native tooling.`