docker-swarm
🐝 Docker Swarm
Swarm mode is Docker's built-in orchestrator: a few managers keep the desired state in a Raft store, and every node's agent reconciles the tasks it runs against it. A stack file looks like a Compose file and is not one — docker stack deploy reads the same format, ignores a good part of it without a warning, and adds a deploy: block that decides how every change reaches production. This skill grades a cluster and its stack files against what Swarm actually does, and designs one that survives a node loss and a bad release.
Swarm, honestly. Swarm mode ships in every Docker Engine (SwarmKit), and it is stable and small. It is also niche: the ecosystem — operators, policy engines, autoscalers, managed offerings — is Kubernetes'. Say which fits before reviewing anything:
| The situation | Recommend |
|---|---|
| One host, a handful of services, downtime on deploy acceptable | Compose on a VM — docker-compose for the stack, container-hardening for running it in production. Swarm on one node adds Raft for nothing |
| 2–20 nodes, a small team, no platform group, stateless services plus one or two datastores | Swarm fits: rolling updates, secrets, overlay networks, built into the engine, little to operate |
| Autoscaling, many teams, admission policy, operators for stateful systems, a managed control plane, or hiring for the skill | Kubernetes. Don't build those on Swarm |
| Already on Swarm and it works | Keep it, review it, and say what would trigger a move — not a migration for fashion |
Where this fits
The container skills; this one picks up where a stack leaves a single host: