|
> first of all, ahrefs discounts the "people" cost, but that's a huge cost to ignore! It's the hardest to compare. Cloud has a significant people cost too, particularly in the complexity. EC2, lambda, S3, RDS, IAM, cognito, glacier, light sail, EBS, fargate, cloud front, SNS, dynamo, elastica he, etc etc. If you ignore this, you fail to completely understand a service you start to use. That's the quickest way to a surprise mammoth bill or insecure service. > they _could_ save significant amounts of money by moving to the cloud AND re-architecting their apps to spend compute more efficiently. This is a bad argument generally. If an org, institutionally, can't properly size services or they leave a lot of fat in their services. Why would a move to the cloud fundamentally change that? You can even more easily over provision and overspend when it's a mere button click away. I fail to see how a move to the cloud basically creates greater institutional ability to trim fat and optimize that just wasn't there before. And I just love how convenient re-architecting is so casually thrown in like it's a walk in the park... Yikes. Rewrites can and do kill companies. Not a casual thing to undertake because a new vendor comes along with a shiny new tool. |