Kelsey Hightower

Borg is this thing that just expands and grows.

Yeah.

In some ways, I guess it's extensible, but all of that insight and knowledge.

But then they get so much experience with that.

If you were to do it again, what would you do?

And you read the Omega paper, and it's like, here's what we learned from scheduling.

It doesn't need to be that complex, especially for certain workloads.

You don't need this high-performance, over-engineered thing.

There's a simpler way to do scheduling, especially if you can give the scheduler a bit more metadata about the workload.

There are also big game changes.

Now, instead of talking about Java versus Python versus Ruby, you only have to talk about scheduling Docker containers.

And so I think that's the number one success criteria that we were already off to a running start because you could just reuse the same Docker containers.

You didn't have to rebuild a new image thing.

So given that, what they tried to do in the early beginning was just fill in the gaps.

And in many ways, yes, it's a new system, but it fills in the gaps.

The one gap that they filled in was Docker had an entry point.

So if you needed a Ruby app that needed Nginx and your process, you used to have to write a little shell script, an entry point script that would do all of this magic, almost imitating an init system.

Kubernetes is like, no, no, no, you don't need to do that.

You can just make separate containers, and then Kubernetes will run them as a process tree.

And so for many people, it's like, finally, now we can have a clear way of thinking about application architecture.