The problem: We broke Warnar.
the state of being formed of many parts; the state of being difficult to understand
It seems to be commonly-held in some circles that tools like Kubernetes bring with them a lot of complexity. "We'll never need those - we're not Google-scale!"
Well, how true is that? What complexity do orchestration tools bring to the table, and where are the trade-offs? Is there actually complexity there, or just the perception of complexity? Can you achieve the same stuff with a couple of VMs and a load balancer?
And most importantly: after this episode, will Warnar ever be the same man again?
- Hacker News comment by FlyingSnake — The more I look into k8s ecosystem, the more I'm convinced that it's one of those things that suits FAANG etc, but the regular Joe developer has caught on the fad and wants to add it to his repertoire, even though it's an overkill.
- Hashicorp Nomad
- Apache Mesos
- Helm - The package manager for Kubernetes
- The Operator pattern - Kubernetes
- Distroless - language focused Docker images, minus the operating system
- AWS Fargate - Serverless for containers
- Google Cloud Run