On the other hand, Dock Inc. failed with its cloud product because it was not able to compete with other cloud providers like Amazon Web Services (AWS), Microsoft Azure, and Google Cloud Platform. Dock Inc. was a startup that was focused on providing a container-based platform for building and deploying applications. However, it was not able to gain traction in the market, and its product was not as mature or feature-rich as those offered by larger cloud providers.
Another reason for Dock Inc.'s failure could be a lack of community support. Kubernetes has a strong community of developers who contribute to the project and help improve it. This has helped to build a robust ecosystem of tools and services around Kubernetes, which has made it easier for developers to adopt it. Dock Inc. may not have had the same level of community support, which could have made it harder for them to gain traction in the market.
There are quite a few optional tools built on the k8s model, like service meshes or tools to orchestrate a postgres cluster.
Swarm is a small piece of that, the scheduling system, and you have to run it yourself. It's really not comparable.
IMHO, Google did something smart/evil here. Google did not use the docker-compose style yaml files for k8s configurations. This turned into a big deal. If you have a docker-compose file and want to run it in k8s - you cannot. So you need to make a decision: go with docker-compose yamls which has no place to be hosted except swarm OR go with k8s yaml style and be able to run it on aws,gcp, etc.
> be the cashcow that turned
> that into cashflow. And then
> k8s happened.
We are still using Docker Swarm in production. It seems to be working fine so I always wondered why it never took off. But I am not a Devop. Can sb please give some insight on why kubernetes took off instead and why Dock Inc. failed with its cloud product?