3 ms·
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?
by zug_zug 2y ago
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.
- stouset 2y agoKubernetes and AWS aren’t alternatives. They occupy vastly different problem spaces.
- zug_zug 2y agoNot really.
- deleted 2y ago[deleted]
- stouset 2y agoSure, what do I know, I only operate the Kubernetes platform (on AWS) that runs most of a $50bn public company.
- zug_zug 2y ago"It is difficult to get a man to understand something when his salary depends on his not understanding it." - Upton Sinclair
- stouset 2y agoMy salary directly depends upon me deeply understanding both AWS and Kubernetes. Better luck next time.
- fknwankr18 2y ago[dead]
- SJC_Hacker 2y agoKubernetes 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.
- zug_zug 2y agoI’ve never seen a single company use kubernetes or terraform to move vendors; the feasibility of that was massively over represented
- SJC_Hacker 2y agoWell we did at my company when we moved from AWS to GCP