3 ms·
In 10 years Google will be a fading memory (one hopes). Once they die, K8s dies. K8s' fatal flaw was being too big for its britches. As individual pieces, none
by throwaway892238 4y ago
In 10 years Google will be a fading memory (one hopes). Once they die, K8s dies.
K8s' fatal flaw was being too big for its britches. As individual pieces, none of the K8s services are useful. Nobody downloads and installs just one of the components for use in some other project. And for that reason, it will always be just one big fat ugly monolith of fake microservices.
The architecture that will come afterward will be the model we've had since the 90s: single components that do their job well, that can be combined with other components in a hobbled-together way, that together make up a robust system. The same thing that lets you build an architecture out of PostgreSQL, Ory, Nginx, Flask, React, Prometheus, ELK, etc: they're all separate, but they can all be combined the way you want, when you want. And they're all optional.
- hsbauauvhabzb 4y agoI can’t help but think this is already here: docker, docker-compose, and proprietary cloud products. You’re not important enough to need a load balancer, and if you are you can use paas elbs and native services. Only once your google scale does k8s make sense.
- bongobingo1 4y ago> single components that do their job well, that can be combined with other components in a hobbled-together way This is sort of Nomad & friends?