That’s basically what put me off trying nomad. Nit just the minimum number, but also their stated hardware requirements. From their documentation:
Nomad servers may need to be run on large machine instances. We suggest having between 4-8+ cores, 16-32 GB+ of memory, 40-80 GB+ of fast disk and significant network bandwidth
Basically the cost if the Nomad masters would be much greater than the cost of what would run my actual applications. That’s a non-starter for me.
> You I think you could be fine with 3 of the smallest machine types.
Maybe, but if that’s their official stance, it would make me very nervous to run a production system with lower spec machines.
They ( and many others ) better pray central banks keep printing money by the ton, because once the crunch comes these IT SUVs will be the first to go.
Maybe there's some element of "geek macho" from their side here, but this is their recommendation for a supporting a "small" workload, where I suspect you find yourself on the very low end of that.
Like, you're not doing "big data" unless we're talking petabytes per day.
It really depends on how what your workload is though.
We have been running between 100 and 200 Jobs in Nomad, with the quantity of clients doubling then shrinking every day using 3 × t3.micro for the servers since years.
We have yet to see our Nomad usage increase enough to get rid of these machines.
Nomad servers may need to be run on large machine instances. We suggest having between 4-8+ cores, 16-32 GB+ of memory, 40-80 GB+ of fast disk and significant network bandwidth
Basically the cost if the Nomad masters would be much greater than the cost of what would run my actual applications. That’s a non-starter for me.
> You I think you could be fine with 3 of the smallest machine types.
Maybe, but if that’s their official stance, it would make me very nervous to run a production system with lower spec machines.