[motoboi]

There is a very high price to pay when going with your own scheduling solution: you have to compete with the resources google and others are throwing at the problem.

Also, there is the market for talent, which is non-existent for fly.io technology if it's not open source (I see what you did here, Google): you'll have to teach people how your solution works internally and congratulations, now you have a global pool of 20 (maybe 100) people that can improved it (if you have really deep pockets, maybe you can have 5 Phd). Damn, universities right now maybe have classes about Kubernetes for undergrad students. Will they teach your internal solution?

So, if a big part of your problem is already solved by a gigantic corporation investing millions to create a pool of talented people, you better take use of that!

Nice move, fly.io!

[nojvek]

What if it’s really not that complicated, and by adding more people you make it more complex. So complex that you need even more people to maintain that complexity?

I love fly.io for rethinking some of the problems.