Hacker News Reader

This is a non sequitur. You can, and should, leverage the flexibility of cloud computing without being too locked down to a single vendor.

That’s one of the things tools like Terraform, Kubernetes or Mesos were designed for.

View on HN

Terraform doesn’t buy you anything. It supports multiple vendors, but you have to re-write all the code when switching.

If the lowest common denominator is K8S/Mesos, while not using any of the cloud services, you’re doing it wrong.

Which would do you have to re-write? Your deployment code or your application code. If it’s the latter you’re not using the cloud correctly. If it’s the former, re-writing deployment scripts is much easy than physically migrating a DC which is think is the real comparison.

I have built multi-cloud, totally cloud-agnostic deployments at my previous company with terraform, for really interesting reasons. At least for tf even if you are spinning up a VM and installing something like postgres on it (cloud agnostic, no managed services), rewriting is required because the order of operations can be different in infrastructure building, different modules, different vars, etc. You can use your code for one cloud as a template for the new one, but you do need to maintain a set of scripts for each cloud in my experience.

Reply on news.ycombinator.com