Item — HN Reader

I think you're sort of hand-waving here.

I think the concrete question is -- do you need to learn more or fewer abstractions to use kubernetes versus say AWS?

And it looks like kubernetes is more abstractions in exchange for more customization. I can understand why somebody would roll their eyes at a system that has as much abstraction as kuberenetes does if their use-case is very concrete - they are scaling a web app based on traffic.

1 comments

Kubernetes and AWS aren’t alternatives. They occupy vastly different problem spaces.

Not really.

Kubernetes isn't locked to any vendor

Try moving your AWS solution to Google Cloud without a massive rewrite.

Also Kubernetes doesn't actually deal with the underlying physical devices, directly. That would be done something like Terraform or if you're still hardcore, shell scripts.

I’ve never seen a single company use kubernetes or terraform to move vendors; the feasibility of that was massively over represented

Well we did at my company when we moved from AWS to GCP

Sure, what do I know, I only operate the Kubernetes platform (on AWS) that runs most of a $50bn public company.

"It is difficult to get a man to understand something when his salary depends on his not understanding it." - Upton Sinclair

My salary directly depends upon me deeply understanding both AWS and Kubernetes. Better luck next time.