4 ms·
I agree with you that if you're looking at single-node deployments, Nomad or any distributed orchestrator will feel like overkill. I personally use Nomad quite
by heipei 5y ago
I agree with you that if you're looking at single-node deployments, Nomad or any distributed orchestrator will feel like overkill. I personally use Nomad quite a lot, but for single-box systems I'll happily revert to using plain Docker containers started via systemd service files.
The beauty of something like Nomad is that you can run it on a single box with moderately more effort than docker compose, but then you can flick a switch and have your workloads run across multiple machines.
- maccard 5y ago> The beauty of something like Nomad is that you can run it on a single box with moderately more effort than docker compose, but then you can flick a switch and have your workloads run across multiple machines. How is that any different to kubernetes with k3s?
- sofixa 5y agok3s is still drastically more complex, with a lot more moving parts.
- maccard 5y agoHonest question; how? And what difference does that make to running an app? Running on k8s involves writing 2 yaml files, and scaling is literally the flick of a switch. The architecture of nomad may be simpler but how does that benefit me as a user? I've been running apps in kubernetes for about 2 years now at a "mild" scale and not once has the complexity of k8s been the show stopping issue it's made out to be here on HN.