4 ms·

I do think it's a fight to the death for container orchestrators. The configuration files required to run complex auto-scaling systems can add up (and require D

I do think it's a fight to the death for container orchestrators. The configuration files required to run complex auto-scaling systems can add up (and require DEEP understanding of all the systems involved and how they interact with each other) - Most developers don't want to have to do it for more than one orchestrator; especially since there is no straightforward migration path from one orchestrator to another. Also, learning different orchestrators is a lot of work. Sure, maybe Mesos does more than just schedule containers, but that doesn't matter because a standardized orchestration platform is the main thing developers need right now - For orchestration to become truly standardized, there needs to be a single big majority winner. It reminds me of the Minix vs Linux debate in the early days of operating systems; Minix was modular (microkernel) while Linux was monolithic. The reason why Linux won is because it provided a single consistent standard platform on which to build and configure applications. I think the same is going to happen here and I think that Kubernetes or Swarm are better placed in that regard.

k2xl 9y ago
I'm not sure if I agree. There are many frameworks in the devops space with each having their own DSLs that had various learning curves. For example, I see companies split between Puppet, Chef, Salt, Ansible, etc... It sucks, don't get me wrong, that there one hasn't come away from the pack, but I don't think it's likely that any of these orchestration frameworks will go away. Each of them have a pretty dedicated following with lots of developers behind it.
tyingq 9y ago
>The reason why Linux won is because it provided a single consistent standard platform I suspect there were many reasons. One reason it might have won vs minix was broader driver support for various video, network, sound cards, etc.
justicezyx 9y ago
> The configuration files required to run complex auto-scaling systems can add up Is there a tool for managing orchestration config? I am very interested in learning the current status.
- elmiko 9y ago
  just watched a demo about http://codesolvent.com/ http://codesolvent.com/ on monday, seems like they are providing a solution for configuration management that is oriented towards cloud orchestration. i'm sure there are others, but this was fresh in my mind

k2xl 9y ago

I'm not sure if I agree. There are many frameworks in the devops space with each having their own DSLs that had various learning curves. For example, I see companies split between Puppet, Chef, Salt, Ansible, etc... It sucks, don't get me wrong, that there one hasn't come away from the pack, but I don't think it's likely that any of these orchestration frameworks will go away. Each of them have a pretty dedicated following with lots of developers behind it.

tyingq 9y ago

>The reason why Linux won is because it provided a single consistent standard platform I suspect there were many reasons. One reason it might have won vs minix was broader driver support for various video, network, sound cards, etc.

justicezyx 9y ago

> The configuration files required to run complex auto-scaling systems can add up Is there a tool for managing orchestration config? I am very interested in learning the current status.

elmiko 9y ago
just watched a demo about http://codesolvent.com/ http://codesolvent.com/ on monday, seems like they are providing a solution for configuration management that is oriented towards cloud orchestration. i'm sure there are others, but this was fresh in my mind