Post

I wish Kubernetes did less. Mesos was a thin layer of resource management & platforms (aka frameworks) had all the opinions on how jobs should run The biggest downside of Mesos was Zookeeper just like the biggest downside of K8s is etcd. If that wasn't there k8s would scale and be easier to manage

Borg is widely adopted because of Google’s org chart and culture From everything I’ve heard it’s overly complicated (feature creep) but internal teams have been layering on top of layers to make specific things easier K8s tries to layer & be flexible (eg deployments) which doesn’t layer well

This is why you see alternative options in k8s. Things like Argo rollouts. Same primitives, different opinions K8s deployments are good enough for a lot of things but once you need something else it is more work than it should be

It's true that getting rid of things in Borg is nigh impossible - someone is using EVERY feature (even when that feature literally does nothing anymore :) Google has a high tolerance for "exposed wiring" sorts of UXes, which is not true in the wider world.

Railway.app built there own orchestration over going with k8. I can’t seem to find the a post on it but remember talk to Jake Cooper on the why’s and it just not fitting for them. Not the exact write up but does point out they went in a different direction. blog.railway.com/p/launch-wee...

They built an orchestrator on top of Temporal??? That has "ansible is good enough" vibes to me I'm going to email them and see if they'll come talk about it on shipit.show

Thought Jake had been on the changelog before but it doesn't look like it. I interviewed with Railway back then he was initially interviewing candidates. Ended up being a fun chat on distributed systems and some of the challenges he had ran into in previous roles. There is youtu.be/0YLNrvy_F70?...