4 ms·
I really worry about cost in this future of leaning on something like ACI/Fargate to actually run the containers. An m5.large instance (2vcpu/8gb) costs $70/mo
by 013a 8y ago
I really worry about cost in this future of leaning on something like ACI/Fargate to actually run the containers.
An m5.large instance (2vcpu/8gb) costs $70/mo on-demand ($44/mo with a 1 year reservation). A similar Fargate runtime costs $146/mo.
A b2ms Azure instance (2vcpu/8gb) costs $60/mo on-demand ($39/mo 1 year reservation). Azure Container Instances at a similar provisioning level costs $176/mo by my calculations.
That's not a small difference. That's, like, 3x.
Point being, I love virtual-kublet from the perspective of a scale-up just trying to get a product out the door. But for established companies, I still think the core idea of a container on a VM you control is going to rule. Fortunately Kubernetes allows amazingly easy flexibility to switch, and that's a reason why it might be the most important technology created in recent history.
- hedora 8y agoAlso, the instance prices are already some crazy multiple of buying a machine, racking it, and running dozens of VM’s on it for 5 years. I don’t know the prices for hyperconverged or converged infrastructure off the top of my head, but doubt the amazon rates are even close to competitive unless you’re at a tiny scale (or need a ton of tiny presences in different regions).