Set up StackOverflow according to "cloud native" recommendations and whoops, that's gonna be quite the bill, which is my point. You'll have Cloudfront for global load balancing, ELB to provide a bridge between Cloudfront and Kubernetes, EFS for storage, RDS for the database, EKS and EC2 for compute, ElastiCache for KV cache, add in CodeBuild for build/deploy pipelines... AWS has quite the hefty overhead.
Oh definitely. AWS is where you go to set money on fire.
However servers aren't the sort of thing you can just plugin and forget when running a major website. Things go down, users trigger edge cases, people try and DOS you, disks fill up, etc. You do still need some staff to take care of things
Set up StackOverflow according to "cloud native" recommendations and whoops, that's gonna be quite the bill, which is my point. You'll have Cloudfront for global load balancing, ELB to provide a bridge between Cloudfront and Kubernetes, EFS for storage, RDS for the database, EKS and EC2 for compute, ElastiCache for KV cache, add in CodeBuild for build/deploy pipelines... AWS has quite the hefty overhead.
Oh definitely. AWS is where you go to set money on fire.
However servers aren't the sort of thing you can just plugin and forget when running a major website. Things go down, users trigger edge cases, people try and DOS you, disks fill up, etc. You do still need some staff to take care of things