Mirantis has published on their blog that they will continue to support and develop Docker Swarm. [Link to the article](https://www.mirantis.com/blog/mirantis-will-continue-to-support-and-develop-docker-swarm/)
Answers to your questions
Mirantis has published on their blog that they will continue to support and develop Docker Swarm. [Link to the article](https://www.mirantis.com/blog/mirantis-will-continue-to-support-and-develop-docker-swarm/)
>Following our acquisition of Docker Enterprise in November 2019, we affirmed at least two years of continued Swarm support, pending discussions with customers. These conversations have led us to the conclusion that our customers want continued support of Swarm without an implied end date. \[…\] To that end, Mirantis will be continuing to invest in active Swarm development.
I mean, considering they’re only willing to ***commit to 24 months of support*** and leaving the rest up to interpretation that’s essentially stating “we have quelled customer fears until they have successfully migrated over to another orchestration solution and can continue milking the thing we own in peace until then”.
\*edit to better reflect the quote
I am very pleased with this announcement. Not only has the community spoken up about Swarm, but the company listened and reacted appropriately.
I’ve personally held off on changing orchestration for my production workloads because Swarm is working so well and is much more simpler for our purpose than the popular alternative.
I’ll speak for many of us with a big sigh of relief that I can stop worrying about converting simple workloads that fit perfectly in swarm into Kubernetes. That being said, this is the tech industry and anything can still happen down the road, so best to stay on your feet and have a backup plan for the worst just in case. 🙂
honestly, after close to five years of Swarm and Kubernetes usage, I still don’t understand why people get so eager to use Kubernetes.
I do use k8s, when the service I want to provide doesn’t work with overlay networks, but for everything else I use Swarm in production with no problems at all.
My services scale when needed, update and rollback if necessary, and as it’s quite trivial to setup, I can have different clusters and play with domain’s weights for A/B testings, etc.
Maybe it’s because I haven’t had millions of clients, but for some hundred of thousands, Swarm has proven to be the most reliable and cost-effective solution for me.
This is good news for companies that run simple workloads and don’t want to heavily invest in Kubernetes.
Does anyone here use Nomad for container orchestration?
Does anyone know a good managed swarm service? Would be nice to have someone ready-packaged, each time we use it we are spinning up a small cluster
This is great to hear, mostly because Docker Compose works so well for local testing and small projects. Kubernetes is great, but it is complicated af and is really best suited for large workloads. I feared having to start using k3s or something like that for local dev and having to write chonky manifests or helm charts
Been calling it for a week now all over /r/docker. Glad we have an official statement and glad Mirantis is continuing to support the community.