4 ms·

Fully agree, this is a typical example of a shitty Swarm/Kubernetes/etc blog post, which gives no real substance - this stuff is covered in first 5 minutes. We

Fully agree, this is a typical example of a shitty Swarm/Kubernetes/etc blog post, which gives no real substance - this stuff is covered in first 5 minutes. We are just deploying our first Kubernetes cluster in production and anything more than basic hello world would be welcome. Like how to configure networking in production, how to route traffic to containers, how to provide volume storage (backups, etc..). I mean, we'll get there of course, but we opted against Swarm as data is even more lacking than Kubernetes.

joshdev 10y ago
I think the main issue is that beyond the very basic examples the new Docker 1.12 swarm features aren't really production ready. At this point there is a significant amount of tooling required to get a production cluster running with your applications. The Distributed Application Bundles (DAB) files, one of the features I was most excited about, are still marked as experimental. Overall I think Docker is heading in the right direction, but for now Kubernetes, ECS, etc... are better solutions for orchestration. I was hoping to only use Docker for my current project, but I think I'll have to wait until the next one rolls around and Docker releases a few more updates.
- gamedna 10y ago
  "Production Ready" is a funny term. Just like any other product, docker swarm will be production ready once we see a whitepaper or writeup that details the scaffolding around it to meet some sort of SLA. I would be willing to build a production cluster of say 20-50 nodes with swarm in order to learn its intricacies. Building anything larger would have to be done incrementally with lots of monitoring and transparency.