4 ms·
(Note: I'm one of the folks who works at HashiCorp) We don't have permission at this time to share some of our big users (we're working on approvals!), but I c
by mitchellh 12y ago
(Note: I'm one of the folks who works at HashiCorp)
We don't have permission at this time to share some of our big users (we're working on approvals!), but I can say that that some very big companies you've certainly heard of and probably use right now have deployed Consul across every server. And Consuls deployment in just companies were working with is in the hundreds of thousands of machines.
At this point were very confident in its stability and it's well proven at very large scale.
If you're a big user and need references to other large users, email me and I'd be happy to set that up.
- ch 12y agoWhen you say hundreds of thousands of machines, is each one running a consul agent, or do some just make use of answers provided via DNS or the remote api? Without divilging too many details, what would be the ratio of agents running '-server' to overall agents?
- sandstrom 12y agoI'm no expert on consul, but I think it's architected such that you'll run a few servers (say 3 or 5) and the rest will be agents. All machines using consul will (generally) run the agent locally.
- ch 12y agoYou have the general topology right, but not all nodes necessarily have to be agents. You could, forinstance, run an agent next to a bind server and delegate the .consul. Zone to it. That way for nodes which only use DNS for discovery can work I modified. In general you are going to set up an N+M topology of n servers and n+m agents -- but for a network of 100k nodes does consul scale to 100k agents? Plus what goes unstated is how those 100k nodes are laid out in DCs and racks. Anyway, this isn't to slag on consul. I think consul is like chocolate and peanut butter. I use it in my mesos cluster and just am genuinely curious how large it can scale!