Consul

23 engineers on Hacker News describe using Consul first-hand: 7 endorse it, 2 regret it, 1 are mixed.

69%trust
23first-hand users
22in production
endorse 7mixed 1regret 2uses, no opinion

“We use consul/vault/nomad at $DAYJOB. It's been a mostly stable platform for us.”

endorse · production · wingmanjd · 2023-12-09 · source ↗ · wrong label?

“some random consul call consumed the port we listen on, a shutdown timeout expired and the process was killed”

regret · production · hinkley · 2023-03-01 · source ↗ · wrong label?

“the consul agent kept reporting it and itself as healthy, and failover and gossip generally wedged”

regret · production · pronoiac · 2021-10-16 · source ↗ · wrong label?

“managing a nomad, consul and vault cluster is easy for us.”

endorse · production · zie · 2020-10-23 · source ↗ · wrong label?

“If you also manage some form of legacy infrastructure and VMs, consul is hard to ignore.”

endorse · production · marketlid · 2020-07-30 · source ↗ · wrong label?

“Nomad + Consul. Used it for years in prod - just awesome.”

endorse · production · jordanbeiber · 2020-05-03 · source ↗ · wrong label?

“consul is a little bit wierd when it comes to services”

mixed · production · merb · 2017-12-06 · source ↗ · wrong label?

“Consul fits the bill. It's HTTP- and DNS-interfaces interest me because they play well with our existing boring tools”

endorse · production · deathanatos · 2015-03-31 · source ↗ · wrong label?

“we switched to consul and so far we are happy with it”

endorse · production · vruiz · 2015-02-10 · source ↗ · wrong label?

“I've been using consul in production since 1.0. I've never had an issue with it - it works great for me!”

endorse · production · s0l1dsnak3123 · 2014-09-30 · source ↗ · wrong label?

“You'll certainly want to combine it with Consul and use Consul templates and service discovery though.”

neutral · production · ChocolateGod · 2024-11-27 · source ↗ · wrong label?

“9x Pi 4B-equivalent ARM SBCs: 3x consul + 3x vault + 3x nomad server.”

neutral · personal · baobun · 2023-12-23 · source ↗ · wrong label?

“In our new configuration management, we're much more coarse about testing. Setup a consul server, setup a patroni cluster”

neutral · production · tetha · 2023-10-12 · source ↗ · wrong label?

“We run high-availability Ceph, Postgres, and Consul, across 3 Hetzner DCs”

neutral · production · 5 yr · nh2 · 2021-12-22 · source ↗ · wrong label?

“each server acting as a load balancer has access to state (backed by Consul) that tells it which flow belongs to which application server.”

neutral · production · matsur · 2021-09-03 · source ↗ · wrong label?

“it seemed to be a combination of Node + Consul DNS”

neutral · production · clarkdave · 2020-02-07 · source ↗ · wrong label?

“the certificate settings are not included in the reloadable settings for our version of Consul”

neutral · production · thaniri · 2019-11-17 · source ↗ · wrong label?

“What about the cost of person-hours we need to spend changing the code everywhere?”

neutral · production · volkandemirel94 · 2019-11-10 · source ↗ · wrong label?

“7 servers for Hashicorp's Consul (1 in Dev,QA, UAT, and a cluster in production).”

neutral · production · scarface74 · 2018-11-08 · source ↗ · wrong label?

“We use consul UI to show all the services that we have, where they're running, number of instances and so on.”

neutral · production · aprdm · 2017-11-24 · source ↗ · wrong label?

“we run around 300-600 containers currently using our implementation using Consul+Serf.”

neutral · production · mrmondo · 2016-07-17 · source ↗ · wrong label?

“I am all in on the Hashicorp stack (we use Vagrant, Packer, Terraform and Consul)”

neutral · production · n42 · 2015-07-08 · source ↗ · wrong label?

“it will register with consul and be added to haproxy”

neutral · production · steveb · 2015-06-12 · source ↗ · wrong label?