![docker swarm vs kubernetes 2018 docker swarm vs kubernetes 2018](https://d3i71xaburhd42.cloudfront.net/adfdfea7b7d27e541c8dc3e31399e543358d5638/3-Figure3-1.png)
Because K8s has a larger community, dedicated conference, and is a media darling, it gets a higher percentage of chatter on the internet then what is representative than the actual number of people doing real work on clusters. They both do 90% of the same stuff if you're going to build a cluster yourself. They can maintain it with a single person's part-time efforts for a dozen or more servers.
![docker swarm vs kubernetes 2018 docker swarm vs kubernetes 2018](https://techniblogic.com/wp-content/uploads/2018/07/Kubernetes-vs-Docker-Swarm-1-1024x420.png)
I have consulting clients using it for real production work for well over a year.
#DOCKER SWARM VS KUBERNETES 2018 FREE#
It's the free open source "core" that drives the cluster features of Docker Enterprise Edition, so it has great support from the Docker team and community in the SwarmKit repo, which is part of the Moby Project. It grows as you grow, and only takes a few commands to have a production-ready cluster. It's built from open source libraries just like K8s, but is delivered in a single binary that is "batteries included, but removable". I think Swarms advantage is in its simplicity. There is a growing list of container orchestrators that are all doing 75%+ the same thing, but that focus on certain areas of the problem space or ecosystem.Swarm and K8s are two solid solutions in a healthy space. An unhealthy space is when there's only one opinion of solving a problem. Just like all other IT tools and frameworks, as we see the market for that tool's problem space mature, we usually end up with a few solid solutions to the problem.First, I don't fundamentally think one is universally better than the other for all people.