Not a big AWS fan or anything, but...
> they rely on bad math capabilities of their clients
No, they don't. Showing hourly prices makes sense for hourly services.
They also provide a detailed cost estimator, because the arithmetic gets pretty detailed: https://calculator.aws
> compared to a root server for $10 that easily outperforms a $60 EC2 instance that's really overpriced.
Let's say a developer costs $75/hr. If AWS saves my dev team 10 hrs/mo., then I'm willing to pay a $750 premium for it.
Developer costs are also unpredictable. Turnover will cause spikes in my costs, for example.
Server costs are predictable. If I need to pay AWS more to save my developers time, I can always do that. I can't always just throw another developer onto my team when I need one.
The only people who are optimizing for three-figure costs every month are either: 1) paying very, very low salaries to their developers, or 2) not thinking about their biggest cost, which is developer time.
> When hosting a simple one-node Kubernetes cluster
Who would do this and why? Why would you have a load balancer in front of a single server?
> they rely on bad math capabilities of their clients
No, they don't. Showing hourly prices makes sense for hourly services.
They also provide a detailed cost estimator, because the arithmetic gets pretty detailed: https://calculator.aws
> compared to a root server for $10 that easily outperforms a $60 EC2 instance that's really overpriced.
Let's say a developer costs $75/hr. If AWS saves my dev team 10 hrs/mo., then I'm willing to pay a $750 premium for it.
Developer costs are also unpredictable. Turnover will cause spikes in my costs, for example.
Server costs are predictable. If I need to pay AWS more to save my developers time, I can always do that. I can't always just throw another developer onto my team when I need one.
The only people who are optimizing for three-figure costs every month are either: 1) paying very, very low salaries to their developers, or 2) not thinking about their biggest cost, which is developer time.
> When hosting a simple one-node Kubernetes cluster
Who would do this and why? Why would you have a load balancer in front of a single server?