[BretFisher]

The difference between reality and Internet news/blogs can sometimes be vast, and we "problem solvers" have to be aware of that. There are hundreds or more enterprise companies using Docker EE, which is using Swarm currently as its orchestrator/scheduler. (see https://www.docker.com/customers) and I also recently ranted about the assumption that everyone is using one thing for orchestration. https://twitter.com/BretFisher/status/958416831659872256

IMO, a healthy ecosystem always has multiple opinions on how to solve a problem.

I'm biased and like Swarm for those that want a great UX (from dev through CI/CD to prod) and their needs match the problems that Swarm solves. I currently teach workshops and consult on Swarm because that's what my circles ask for. It doesn't make anyone wrong or better. These are all opinions on how to create container clusters and some teams like Mesos/DCOS, some Swarm, and some Kubernetes.

In the end, does Swarm solve your problems? If so, stick with it until it doesn't. Docker has publicly stated on their blog months ago that they are not EOL'ing Swarm, despite the news falsely stating Swarms demise. In Docker's main paid product, Docker EE, their new Kubernetes integration actually uses Swarm to help ease K8s deployment AFAIK, so at this point, I feel its future is solid and don't have a problem using it or recommending it. It's still early days for the ecosystem through, so I might be singing a different tune in two years. Swarm may not be the most talked about container orchestrator, but like others, it does solve problems for many people.