Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think you could disregard a few of these without too much thought. Nginx - predatory vendor, AWS - only makes sense if you need the deep integration, Consul - only makes sense if you are on the hashi stack. Traefik I haven't spent much time with recently, but I'm a bit suspect of ingresses that reposition themselves as mesh to gain adoption.


> Consul - only makes sense if you are on the hashi stack.

As an enterprise Hashistack customer, every time I contact Consul support, they assume I'm using Kubernetes instead of Nomad, and when I tell them I'm using Nomad, I get blank stares.

Vault is great, and Consul is...fine, but the Consul PMs saw which way the orchestrator market was trending (towards k8s domination) and have adjusted their priorities accordingly. But if I had my way, I wouldn't touch the Nomad+Consul stack with a 20-foot pole ever again.


Also a Hashistack enterprise customer and we have the same experience.

Thankfully we don't have to talk to Consul support very often, but each time we meet with Consul product people it's like they don't even know Nomad exists.

We're starting to adopt Consul Service Mesh with Nomad and I am not excited.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: