[LoSboccacc]

I agree, looked into swarm and routing was a mess, even discounting the bugs, lockups and moments of total disconnections, you had to rely on ugly dns hacks to know the live endpoints, making any kind of stateful service a nightmare to set up, while kubernet just give you an endpoint api, and even then, there were no guarantees for local services that swarm mesh would route the calls to the local instances, while in kubernet you can control precisely how services are resolved grouping them in pods, so that they don't needlessly clog the pipes.

I find very hard to find swarm use case that a wan, vpn, private segment or kubernet cluster can't handle better.

[netsectoday]

I've been using Docker Swarm in production for about 2 years now... processing about 1TB of data / month across 30+ containers. The networking and routing has been rock solid except for that one day that the Docker dev team, in one release, accidentally added random hashes to the internal DNS names of services. Ever since that day I've used the docker-compose network alias for internal routing https://docs.docker.com/compose/compose-file/#aliases

Discovering bugs in a technology you just started "looking into" actually sounds like the learning curve.

[LoSboccacc]

are you sure you're not mixing swarm and swarm mode?

[netsectoday]

Apparently out of Swarm, Swarmkit, and SwarmNext; my good experience has been from SwarmNext. So now this is even more confusing.

[mosselman]

Ok, there is a difference? Do you have links to docs of both? This sounds hard to search for online.

[LoSboccacc]

https://sreeninet.wordpress.com/2016/07/14/comparing-swarm-s...

[GordonS]

Surprised to hear this, as I've been running a 3-node Swarm cluster for a couple of years now, and it's worked perfectly - and it's so much simpler than k8s.