3 ms·

So the main question I have is... Obviously someone has to do the invention. How will this pan out after all these container tools settle? What if Kubernetes i

So the main question I have is... Obviously someone has to do the invention. How will this pan out after all these container tools settle? What if Kubernetes is it? The primary solid implementation of the hardest parts of distributed state management. Google uses this to power GCE, Amazon supports plugging this into ECS, and anyone building their own data center uses it for a control plane. Is this the dream? Or is this a bad outcome for lack of technology diversity?

bradgessler 11y ago
I've used both Kubernetes and ECS. In my opinion, both of those are still pretty raw for developers. There's a lot of generating configuration files (which need to be understood) and configuration that's best left to a DevOps team. Want to setup an ECS cluster? You have to understand VPC, EC2, IAM, CloudFormation etc. Google's situation is a little better, but there's still a lot to understand and some weirdness around connecting that cluster to a cloud MySQL database. If you look at what Convox is shooting for, its sensible defaults. Developers should be able to put together a docker-compose.yml file that describes their infrastructure services and deploy that into some stack that can figure it out. They just need to know a few convox commands without having to understand the bajillion pieces in the AWS stack that would have to be put together manually. At the very least, convox will force all of these other clustering tools to simplify and think more about the developer experience, which is a net win for the entire ecosystem.