Live data from Hacker News

Nomad vs. Kubernetes

nomadproject.io

11–20 of 369 posts

Re: Nomad vs. Kubernetes

#11
Been running Nomad for a while now at work and home, and it is such a fun project to work and tinker with. Great community, lots of plugins and other great stuff. After running k8s in prod and home Nomad felt like a breath of fresh air in all aspects.

Re: Nomad vs. Kubernetes

#12

I assume that Nomad is simpler since the other features are provided by other hashi corp tools (e.g. secrets, auth, etc).

Indeed, the focus is different for the two tools, something that is outlined with more words in the opening paragraph of this very submission:

> Kubernetes aims to provide all the features needed to run Linux container-based applications including cluster management, scheduling, service discovery, monitoring, secrets management and more.

> Nomad only aims to focus on cluster management and scheduling and is designed with the Unix philosophy of having a small scope while composing with tools like Consul for service discovery/service mesh and Vault for secret management.

Re: Nomad vs. Kubernetes

#13

I assume that Nomad is simpler since the other features are provided by other hashi corp tools (e.g. secrets, auth, etc).

In my experience you end up needing additional tools for everything in Kubernetes such as secrets, auth, etc. that’s the pluggable API selling point.

Re: Nomad vs. Kubernetes

#14
post #2

As a Xoogler it's always seemed weird to me how Kubernetes was compared to Borg. Kubernetes covers a much larger set of things than Borg alone, and I don't necessarily think that's for the better. Being written in a language that isn't well-suited to large projects and refactoring efforts doesn't help either. Nowadays I don't have use-cases for either, but from playing around with Nomad it felt a lot more "Borg-y" th…

> I rarely hear anything about the Hashicorp alternative for service discovery and such though, so it would be interesting how that compares.

Consul is used for service discovery. Fast, reliable and easily extensible. Yet to have a serious issue with it.

Re: Nomad vs. Kubernetes

#15
There seems to be plenty of reasons to run Nomad, compared to Kubernetes, but in what scenarios do Nomad lose out to Kubernetes?

Is it simply a matter of Kubernetes being an open source project and Nomad being owned by HashiCorp?

Re: Nomad vs. Kubernetes

#16
post #8

Earlier quoted context omitted.

Borg is C++.

There you Go (pun intended). Go even replaced a low-level language like C++ and achieved the same result in the end. I don't know why I thought it's Java, probably the first Kube was initially in Java. It's even better that they managed to pull that off.

But it did not replace it. Google runs on Borg. Go lets you build things fast, but the lack of strong typing and the vast amount of language pitfalls make maintenance hard in the long run.

The community also has the attitude to pretend that these pitfalls don't actually exist, which is very different from C++ where most peculiar behaviours are well-understood and controlled.

Re: Nomad vs. Kubernetes

#17

There seems to be plenty of reasons to run Nomad, compared to Kubernetes, but in what scenarios do Nomad lose out to Kubernetes? Is it simply a matter of Kubernetes being an open source project and Nomad being owned by HashiCorp?

Nomad is an open source project as well though.

Re: Nomad vs. Kubernetes

#18
post #8

Earlier quoted context omitted.

Borg is C++.

There you Go (pun intended). Go even replaced a low-level language like C++ and achieved the same result in the end. I don't know why I thought it's Java, probably the first Kube was initially in Java. It's even better that they managed to pull that off.

> Go even replaced a low-level language like C++ and achieved the same result in the end

Did it, though? Honest question. I get the feeling that it ended up competing with Java (and Python) more than it ended up replacing C++. The C++ folks seem to be way more into Rust than Go.

Re: Nomad vs. Kubernetes

#19

There seems to be plenty of reasons to run Nomad, compared to Kubernetes, but in what scenarios do Nomad lose out to Kubernetes? Is it simply a matter of Kubernetes being an open source project and Nomad being owned by HashiCorp?

> There seems to be plenty of reasons to run Nomad, compared to Kubernetes, but in what scenarios do Nomad lose out to Kubernetes?

It would also be interesting if Docker's Swarm was.also featured in this comparison, as it just works right out of the box and doesn't come with any bells and whistles.

Re: Nomad vs. Kubernetes

#20

Nomad seems much simpler to use and manage if you need to do simpler things, but Kubernetes allows you to do more. We use Kubernetes instead of Nomad at work but we are also using Consul in the Kubernetes cluster.

Nomad will still get you where you need to be. Aside from vm live migration i am yet to find a good example of a workload where nomad is straight up is unable to do what you need.
Post reply on HN