4 ms·
> Does cause one to think what the next cycle will entail though... I've just spent a couple of years doing various small projects in AWS and Azure. They're...
by jiggawatts 5y ago
> Does cause one to think what the next cycle will entail though...
I've just spent a couple of years doing various small projects in AWS and Azure. They're... okay. Good, but not great. Proprietary. Closed-source. Etc, etc...
All of that makes me suspect that eventually the cloud will be commoditized and end up being based on a common standard. Kubernetes may or may not become that standard. It certainly feels like the early days of POSIX and Linux starting to slowly take over the proprietary Solaris, HP-UX, and SCO Unix shops.
Something to note is the Kubernetes is already a cloud-within-a-cloud. It has reinvented half of the commonly used Azure/AWS components: Resource groups, storage management, monitoring, naming, tagging, DNS, IP allocation, etc...
Why should I define my resources in Azure, and then again in Kubernetes?
You can see where this is leading: new cloud providers will appear, and they will be Kubernetes only. Instead of proprietary template languages, simply upload your helm chart instead. No complex virtual networking, just use IPv6 and let Kubernetes take care of the rest.
- ghshephard 5y agoAs long as you touch 0.0% of their native services, Isn't that where we are already to some degree with GKE/AKS/EKS? Admittedly, networking/ingress/storage continue to be pretty platform specific. But in theory, as those platforms mature, being able to provide "k8s dialtone" would seem to be attractive. I'm just wondering what comes after k8s itself - though I suspect we're looking at a minimum 15-20 year runway.